From: Jeff Garzik <jeff@garzik.org>
To: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
len.brown@intel.com, gregkh@suse.de
Subject: Recent x86-64 patch causes many devices to disappear
Date: Fri, 26 May 2006 05:53:36 -0400 [thread overview]
Message-ID: <4476D020.8070605@garzik.org> (raw)
The following patch made A TON of devices disappear on my HP XW9300
system. I complained the day it was committed, but alas...
> commit 5491d0f3e206beb95eeb506510d62a1dab462df1
> Author: Andi Kleen <ak@suse.de>
> Date: Mon May 15 18:19:41 2006 +0200
>
> [PATCH] i386/x86_64: Force pci=noacpi on HP XW9300
>
> This is needed to see all devices.
Finally, I was able to get to testing it, and provide proof that a
shitload of devices do indeed disappear:
http://gtf.org/garzik/dammit/
Files:
*.rc4 - rc4, plus some libata changes, PCI domains disabled
*.rc5 - rc5-git1, PCI domains disabled
*.rc5-pcidom - rc5-git1, PCI domains enabled
As the patch doesn't work, and the description is proven patently false,
maybe we can now consider reverting it and making a better patch? My
Marvell SATA and MPT Fusion devices are no longer available, as a diff
between lspci.rc5 and lspci.rc5-pcidom demonstrates.
Jeff
next reply other threads:[~2006-05-26 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 9:53 Jeff Garzik [this message]
2006-05-26 10:03 ` Recent x86-64 patch causes many devices to disappear 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
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=4476D020.8070605@garzik.org \
--to=jeff@garzik.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=len.brown@intel.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 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.