lkml.org 
[lkml]   [2006]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300
Date
On Tuesday 16 May 2006 20:33, Deguara, Joachim wrote:
> > -----Original Message-----
> > From: Jeff Garzik [mailto:jeff@garzik.org]
> > 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-05-16 21:07    [W:0.033 / U:0.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site