From: Len Brown <len.brown@intel.com>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.4] fix "pci=noacpi" boot option
Date: 20 Oct 2003 23:32:35 -0400 [thread overview]
Message-ID: <1066707154.2904.89.camel@dhcppc4> (raw)
In-Reply-To: <200310142328.59083.schlicht@uni-mannheim.de>
On Tue, 2003-10-14 at 17:28, Thomas Schlichter wrote:
> Hi Len,
>
> some time ago I sent a patch which fixed problems with the "pci=noacpi" boot
> option of the 2.5.xx linux-kernel. It got applied to the 2.5 kernel tree but
> I missed to create a similar fix for the 2.4 tree which seems to have the
> same issue.
>
> Now I've seen reports of people having problems with the "pci=noacpi" boot
> option with current 2.4.xx kernel versions, too. So I ported my old patch to
> 2.4.22-bk34, tested it and attached it to this mail. You may consider pushing
> it to Marcelo.
>
> Kind regards,
> Thomas
Thanks for the reminder Thomas, you're correct that pci=noacpi is
broken, see http://bugzilla.kernel.org/show_bug.cgi?id=1219
Note that pci=noacpi is a bug workaround.
It is a bug when a platform requires it. The bug should be filed, root
caused, and fixed. If you know of such platforms, please be encouraged
to file bugs with the details so we can get to the bottom of it.
thanks,
-Len
ps. #include std-acpi-interrupt-bug-info-reqeust.h
Please file a bug at http://bugzilla.kernel.org/
Category: Power Management
Component: ACPI
Please attach the output from dmidecode, available in /usr/sbin/, or
here:
http://www.nongnu.org/dmidecode/
Please attach the output from acpidmp, available in /usr/sbin/, or in
here
http://www.intel.com/technology/iapc/acpi/downloads/pmtools-20010730.tar.gz
Please attach /proc/interrupts and the dmesg output showing the failure,
if possible.
prev parent reply other threads:[~2003-10-21 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 21:28 [PATCH][2.4] fix "pci=noacpi" boot option Thomas Schlichter
2003-10-21 3:32 ` Len Brown [this message]
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=1066707154.2904.89.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schlicht@uni-mannheim.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox