lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080410175455.GA16754@linuxace.com>
Date:	Thu, 10 Apr 2008 10:54:55 -0700
From:	Phil Oester <kernel@...uxace.com>
To:	Michael Chan <mchan@...adcom.com>
Cc:	netdev <netdev@...r.kernel.org>
Subject: Re: bnx2 probe order change from 2.6.21 -> 2.6.24

On Thu, Apr 10, 2008 at 11:45:16AM -0700, Michael Chan wrote:
> On Thu, 2008-04-10 at 08:44 -0700, Phil Oester wrote:
> > I recently upgraded a Dell Poweredge 1950 from 2.6.21 to 2.6.24, and
> > found
> > that the onboard Broadcom NetXtreme II nics got probed in the reverse
> > order.
> 
> I know there is a difference in PCI probing order between 2.4 and 2.6
> kernels on x86 machines, but I'm not aware of changes in these 2 recent
> 2.6 kernels you mentioned above.  Various kernel parameters such as
> pci=nosort, pci=bfsort, pci=nobfsort can affect the order.  Are you
> using any of these?

No - nothing like that.  And the e1000 devices in the box (eth0 - 7) are probing
in the same order, which (perhaps incorrectly) leads me to believe it's not
PCI related, but specific to bnx2.

Phil
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ