All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	len.brown@intel.com, gregkh@suse.de, trenn@suse.de,
	joachim deguara <joachim.deguara@amd.com>
Subject: Re: Recent x86-64 patch causes many devices to disappear
Date: Fri, 26 May 2006 07:08:35 -0400	[thread overview]
Message-ID: <4476E1B3.8020605@garzik.org> (raw)
In-Reply-To: <200605261255.27471.ak@suse.de>

Andi Kleen wrote:
> On Friday 26 May 2006 12:29, Jeff Garzik wrote:
>> Andi Kleen wrote:
>>> The problem is that most people cannot figure out how 
>>> to disable this in the BIOS so we needed a way to make it boot
>>> out of the box.
>> Agreed.
> 
> Do you use SCSI on your box? According to Joachim booting with 
> segmentation on and not pci=noacpi SCSI is not seen. And that's the 
> default setup on the machine which made it unusable.

Here, I see:

	segmentation on + pci=noacpi == no SCSI
and additionally
	segmentation on + pci=noacpi == no sata_mv
and thus overall
	segmentation on + pci=noacpi == no PCI-X bus

(as the posted output on gtf.org shows)

Regards,

	Jeff



  reply	other threads:[~2006-05-26 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-26  9:53 Recent x86-64 patch causes many devices to disappear Jeff Garzik
2006-05-26 10:03 ` Andi Kleen
2006-05-26 10:23   ` Jeff Garzik
2006-05-26 10:25     ` Jeff Garzik
2006-05-26 10:29   ` Jeff Garzik
2006-05-26 10:55     ` Andi Kleen
2006-05-26 11:08       ` Jeff Garzik [this message]
2006-05-26 14:34         ` Thomas Renninger

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=4476E1B3.8020605@garzik.org \
    --to=jeff@garzik.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=joachim.deguara@amd.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=trenn@suse.de \
    /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.