From: "Michael Chan" <mchan@broadcom.com>
To: "Phil Oester" <kernel@linuxace.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: bnx2 probe order change from 2.6.21 -> 2.6.24
Date: Thu, 10 Apr 2008 11:45:16 -0700 [thread overview]
Message-ID: <1207853118.5557.6.camel@dell> (raw)
In-Reply-To: <20080410154401.GA14486@linuxace.com>
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?
next prev parent reply other threads:[~2008-04-10 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 15:44 bnx2 probe order change from 2.6.21 -> 2.6.24 Phil Oester
2008-04-10 18:44 ` Jim Westfall
2008-04-16 15:51 ` Phil Oester
2008-04-10 18:45 ` Michael Chan [this message]
2008-04-10 17:54 ` Phil Oester
2008-04-10 19:15 ` Michael Chan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1207853118.5557.6.camel@dell \
--to=mchan@broadcom.com \
--cc=kernel@linuxace.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).