From: Phil Oester <kernel@linuxace.com>
To: Narendra_K@Dell.com
Cc: linux-kernel@vger.kernel.org, Jordan_Hargrave@Dell.com,
jbarnes@virtuousgeek.org
Subject: Re: [PATCH] Fix embedded nic order on Dell PowerEdge systems
Date: Sat, 9 Jul 2011 20:32:43 -0700 [thread overview]
Message-ID: <20110710033243.GA12541@linuxace.com> (raw)
In-Reply-To: <E31FB011129F30488D5861F3839049151DA349A086@BLRX7MCDC201.AMER.DELL.COM>
On Thu, Jun 09, 2011 at 01:03:00AM -0700, Narendra_K@Dell.com wrote:
> > -----Original Message-----
> > From: Phil Oester [mailto:kernel@linuxace.com]
> > Sent: Thursday, June 09, 2011 1:44 AM
> > To: linux-kernel@vger.kernel.org
> > Cc: K, Narendra; Hargrave, Jordan; jbarnes@virtuousgeek.org
> > Subject: [PATCH] Fix embedded nic order on Dell PowerEdge systems
> >
> > In commit 6e8af08dfa40b747002207d3ce8e8b43a050d99f ("PCI: enable
> > pci=bfsort
> > by default on future Dell systems"), the callback added was placed at the
> > top of the list, before the specific PowerEdge models. This ends up
> > breaking the more specific models listed, since the new callback handles
> > all Dell systems but the older systems don't have the new 0xB1 smbios
> > entry.
> >
> > Fix this by placing the new check _after_ the more specific PowerEdge
> > sytems.
> >
> > Phil Oester
> >
> > Signed-off-by: Phil Oester <kernel@linuxace.com>
> >
> > diff --git a/arch/x86/pci/common.c b/arch/x86/pci/common.c index
> > 5fe7502..92df322 100644
> > --- a/arch/x86/pci/common.c
> > +++ b/arch/x86/pci/common.c
> > @@ -247,13 +247,6 @@ static const struct dmi_system_id __devinitconst
> > pciprobe_dmi_table[] = {
> > },
> > #endif /* __i386__ */
> > {
> > - .callback = find_sort_method,
> > - .ident = "Dell System",
> > - .matches = {
> > - DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc"),
> > - },
> > - },
> > - {
> > .callback = set_bf_sort,
> > .ident = "Dell PowerEdge 1950",
> > .matches = {
> > @@ -294,6 +287,13 @@ static const struct dmi_system_id __devinitconst
> > pciprobe_dmi_table[] = {
> > },
> > },
> > {
> > + .callback = find_sort_method,
> > + .ident = "Dell System",
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc"),
> > + },
> > + },
> > + {
> > .callback = set_bf_sort,
> > .ident = "HP ProLiant BL20p G3",
> > .matches = {
> [>]
>
> Hi, this issue is fixed and the fix is in Jesse's linux-next tree.
>
> http://marc.info/?l=linux-pci&m=130108034729082 (x86/PCI: Preserve existing pci=bfsort whitelist for Dell systems)
>
> With regards,
> Narendra K
This patch is still not included in 3.0.0-rc6, nor in any stable series.
Some reason for this? And did Dell do any testing at all on existing
hardware before submitting 6e8af08dfa4? Seems even a minor amount of
testing should have shown this regression.
Given 3.0.0 is expected soon, perhaps this can be included? Jesse?
Phil
next prev parent reply other threads:[~2011-07-10 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 20:14 [PATCH] Fix embedded nic order on Dell PowerEdge systems Phil Oester
2011-06-09 8:03 ` Narendra_K
2011-06-09 14:11 ` Phil Oester
2011-07-10 3:32 ` Phil Oester [this message]
2011-07-11 12:22 ` Narendra_K
2011-07-22 15:44 ` Jesse Barnes
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=20110710033243.GA12541@linuxace.com \
--to=kernel@linuxace.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@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