public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Jeff Garzik <jeff@garzik.org>,
	"Deguara, Joachim" <joachim.deguara@amd.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300
Date: Tue, 16 May 2006 19:07:42 +0200	[thread overview]
Message-ID: <200605161907.42826.ak@suse.de> (raw)
In-Reply-To: <4469FB26.5070605@garzik.org>

On Tuesday 16 May 2006 18:17, Jeff Garzik wrote:
> Linux Kernel Mailing List wrote:
> > commit 5491d0f3e206beb95eeb506510d62a1dab462df1
> > tree 5c4aadcfb4a93535e2f6e0f5977e930ccacec0e9
> > parent f0fdabf8bf187c9aafeb139a828c530ef45cf022
> > author Andi Kleen <ak@suse.de> Mon, 15 May 2006 18:19:41 +0200
> > committer Linus Torvalds <torvalds@g5.osdl.org> Tue, 16 May 2006 21:59:31 -0700
> > 
> > [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300
> > 
> > This is needed to see all devices.
> > 
> > The system has multiple PCI segments and we don't handle that properly
> > yet in PCI and ACPI. Short term before this is fixed blacklist it to
> > pci=noacpi.
> > 
> > Acked-by: len.brown@intel.com
> > Cc: gregkh@suse.de
> > Signed-off-by: Andi Kleen <ak@suse.de>
> > Signed-off-by: Linus Torvalds <torvalds@osdl.org>
> > 
> >  arch/i386/kernel/acpi/boot.c |    8 ++++++++
> >  1 files changed, 8 insertions(+)
> > 
> > diff --git a/arch/i386/kernel/acpi/boot.c b/arch/i386/kernel/acpi/boot.c
> > index 40e5aba..daee695 100644
> > --- a/arch/i386/kernel/acpi/boot.c
> > +++ b/arch/i386/kernel/acpi/boot.c
> > @@ -1066,6 +1066,14 @@ static struct dmi_system_id __initdata a
> >  		     DMI_MATCH(DMI_PRODUCT_NAME, "TravelMate 360"),
> >  		     },
> >  	 },
> > +	{
> > +	 .callback = disable_acpi_pci,
> > +	 .ident = "HP xw9300",
> > +	 .matches = {
> > +		    DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
> > +		    DMI_MATCH(DMI_PRODUCT_NAME, "HP xw9300 Workstation"),
> 
> Strong NAK.  Please revert.  This majorly screws my primary workstation, 
> and many other users with this workstation.

Did you test that? I had two persons with that workstation test all combinations
and it worked for them. 

Wait - you have a engineering sample haven't you? I don't think i care about
those. Maybe they behave differently. Use pci=acpi

[Don't try to update the BIOS either - it can be deadly]

> At a minimum, you should test to see if the BIOS has activated PCI 
> domain support first!

It worked in both cases on the production system. Without pci=noacpi
the PCI-X bus couldn't be seen.

-Andi
 

  reply	other threads:[~2006-05-16 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605161559.k4GFx3Mi017163@hera.kernel.org>
2006-05-16 16:17 ` [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300 Jeff Garzik
2006-05-16 17:07   ` Andi Kleen [this message]
2006-05-16 17:12     ` Jeff Garzik
2006-05-16 17:23       ` Andi Kleen
2006-05-16 17:25         ` Jeff Garzik
2006-05-16 18:33 Deguara, Joachim
2006-05-16 19:04 ` Andi Kleen
2006-05-17  9:21 ` 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=200605161907.42826.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=joachim.deguara@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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