public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Deguara, Joachim" <joachim.deguara@amd.com>
Cc: "Jeff Garzik" <jeff@garzik.org>,
	"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: Wed, 17 May 2006 11:21:01 +0200	[thread overview]
Message-ID: <200605171121.02202.ak@suse.de> (raw)
In-Reply-To: <2B2475CC03BBA543AF1B9A19AF46443111FFED@sefsexmb1.amd.com>


> 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) 

  parent reply	other threads:[~2006-05-17 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 18:33 [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300 Deguara, Joachim
2006-05-16 19:04 ` Andi Kleen
2006-05-17  9:21 ` Andi Kleen [this message]
     [not found] <200605161559.k4GFx3Mi017163@hera.kernel.org>
2006-05-16 16:17 ` Jeff Garzik
2006-05-16 17:07   ` Andi Kleen
2006-05-16 17:12     ` Jeff Garzik
2006-05-16 17:23       ` Andi Kleen
2006-05-16 17:25         ` Jeff Garzik

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=200605171121.02202.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