> -----Original Message-----
> From: Jeff Garzik [mailto:[email protected]]
> Sent: 16 May 2006 19:25
> To: Andi Kleen
> Cc: Deguara, Joachim; Linux Kernel Mailing List; Linus
> Torvalds; Andrew Morton
> Subject: Re: [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300
>
> Andi Kleen wrote:
> > On Tuesday 16 May 2006 19:12, Jeff Garzik wrote:
> >> Andi Kleen wrote:
> >>> Did you test that? I had two persons with that
> workstation test all
> >>> combinations and it worked for them.
> >> Not yet, it's queued for my next test run.
> >
> > You complained without testing anything?
>
> When I first got the box, pci=noacpi made mmconfig space go
> away, or some other breakage. If your patch forces that,
> then logically that condition should reappear by default.
>
> Jeff
>
The fix worked for me. But as I noted, the lspci output changed and
going back I see the PCI-X bridge went AWOL, though the the SCSI
controller (part of that bug) is PCI-X non-bridge anyway. Also I tested
this with the SLES kernel which IIRC has mmconfig off by default. So
Jeff, I am interested to hear how your testing goes.
-joachim
On Tuesday 16 May 2006 20:33, Deguara, Joachim wrote:
> > -----Original Message-----
> > From: Jeff Garzik [mailto:[email protected]]
> > Sent: 16 May 2006 19:25
> > To: Andi Kleen
> > Cc: Deguara, Joachim; Linux Kernel Mailing List; Linus
> > Torvalds; Andrew Morton
> > Subject: Re: [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300
> >
> > Andi Kleen wrote:
> > > On Tuesday 16 May 2006 19:12, Jeff Garzik wrote:
> > >> Andi Kleen wrote:
> > >>> Did you test that? I had two persons with that
> > workstation test all
> > >>> combinations and it worked for them.
> > >> Not yet, it's queued for my next test run.
> > >
> > > You complained without testing anything?
> >
> > When I first got the box, pci=noacpi made mmconfig space go
> > away, or some other breakage. If your patch forces that,
> > then logically that condition should reappear by default.
> >
> > Jeff
> >
>
> The fix worked for me. But as I noted, the lspci output changed and
> going back I see the PCI-X bridge went AWOL, though the the SCSI
> controller (part of that bug) is PCI-X non-bridge anyway. Also I tested
> this with the SLES kernel which IIRC has mmconfig off by default. So
> Jeff, I am interested to hear how your testing goes.
But PCI-X reappears when you disable the PCI segmentation in the BIOS
right?
-Andi
> The fix worked for me. But as I noted, the lspci output changed and
> going back I see the PCI-X bridge went AWOL, though the the SCSI
> controller (part of that bug) is PCI-X non-bridge anyway. Also I tested
> this with the SLES kernel which IIRC has mmconfig off by default. So
> Jeff, I am interested to hear how your testing goes.
Didn't you guys tell me earlier the machine doesn't boot without
pci=noacpi and segmentation enabled? And now it suddenly does again?
If it works without that option in all cases the patch can be of course
dropped.
-Andi (confused)