From: Greg KH <gregkh@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Andy Whitcroft <apw@shadowen.org>,
Dave Hansen <haveblue@us.ibm.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] i386: run BIOS PCI detection before direct
Date: Wed, 22 Mar 2006 14:08:17 -0800 [thread overview]
Message-ID: <20060322220817.GA13453@suse.de> (raw)
In-Reply-To: <200603221410.47505.ak@suse.de>
On Wed, Mar 22, 2006 at 02:10:47PM +0100, Andi Kleen wrote:
> On Friday 17 March 2006 11:38, Andy Whitcroft wrote:
> > Dave Hansen wrote:
> > > from 2.6.16-rc3-mm1 through at least 2.6.16-rc6-mm1 a patch from
> > > Andi Kleen, titled
> > >
> > > x86_64-i386-pci-ordering.patch
> > >
> > > which is now called:
> > >
> > > gregkh-pci-pci-give-pci-config-access-initialization-a-defined-ordering.patch
> > >
> > > has caused a 4-way PIII Xeon (non-NUMA) to stop detecting its SCSI
> > > card. I believe this is also the issue keeping -mm from booting
> > > on "elm3b67" from http://test.kernel.org/.
> > >
> > > The following patch reverts the ordering of the PCI detection code
> > > to always run the BIOS initialization, first. As far as I can
> > > tell, this was the original behavior, and it makes my machine boot
> > > again.
> > >
> > > Signed-off-by: Dave Hansen <haveblue@us.ibm.com>
> >
> > Ran this through the nightly regression suite on the affected machine
> > and it boots fine with this patch applied.
>
> I fixed this up my copy of the patch.
>
> Also fixed the warning with CONFIG_ACPI=n
Care to send me that copy of the patch so I can forward it on?
thanks,
greg k-h
next prev parent reply other threads:[~2006-03-22 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 0:03 [PATCH] i386: run BIOS PCI detection before direct Dave Hansen
2006-03-17 10:38 ` Andy Whitcroft
2006-03-22 13:10 ` Andi Kleen
2006-03-22 22:08 ` Greg KH [this message]
2006-03-22 21:37 ` Andi Kleen
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=20060322220817.GA13453@suse.de \
--to=gregkh@suse.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=haveblue@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.