netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Jim Westfall <jwestfall@surrealistic.net>
Cc: netdev@vger.kernel.org, mchan@broadcom.com
Subject: Re: bnx2 probe order change from 2.6.21 -> 2.6.24
Date: Wed, 16 Apr 2008 08:51:01 -0700	[thread overview]
Message-ID: <20080416155101.GA26072@linuxace.com> (raw)
In-Reply-To: <20080410184455.GL84358@surrealistic.net>

On Thu, Apr 10, 2008 at 11:44:55AM -0700, Jim Westfall wrote:
> Phil Oester <kernel@linuxace.com> wrote [04.10.08]:
> > 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.
> 
> We ran into this issue as well when going from 2.6.20 to 2.6.23 on dell 
> 1950/2950s.
> 
> If you check your dmesg output from your older kernel you should see
> 
> PCI: Dell PowerEdge 1950 detected, enabling pci=bfsort.
> 
> With the newer kernel the code path that triggers the above is removed if 
> you have ACPI enabled in the kernel.

Thanks.  This was caused by commit 08f1c192c3c32797068bfe97738babb3295bbf42
(x86-64: introduce struct pci_sysdata to facilitate sharing of ->sysdata).

I've sent something along to the kernel list.

Phil

  reply	other threads:[~2008-04-16 15:51 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 [this message]
2008-04-10 18:45 ` Michael Chan
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=20080416155101.GA26072@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=jwestfall@surrealistic.net \
    --cc=mchan@broadcom.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).