From: Samuel Flory <sflory@rackable.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: "Feldman, Scott" <scott.feldman@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: More 2.4.22pre10 ACPI breakage
Date: Wed, 06 Aug 2003 09:50:26 -0700 [thread overview]
Message-ID: <3F3131D2.7050009@rackable.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE009FC0C@hdsmsx402.hd.intel.com>
Brown, Len wrote:
>If it still fails with the latest BIOS (11.0)
>http://support.intel.com/support/motherboards/server/se7501br2/
>
>
I will need to check on that.
>Please be encouraged to file a bug at bugzilla.kernel.org
>Component: ACPI
>Owner: linux-acpi@unix-os.sc.intel.com
>If you can drop in the good/bad dmesg, lspci, and /proc/interrupts,
>That would be great.
>
>Thanks,
>-Len
>
>Ps. If it is an ACPI interrupt config problem, it should boot also with
>pci=noacpi
>
>
>
It boots fine with acpi=no. I did not try pci=noacpi
next prev parent reply other threads:[~2003-08-06 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 16:16 More 2.4.22pre10 ACPI breakage Brown, Len
2003-08-06 16:50 ` Samuel Flory [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-06 2:04 Feldman, Scott
2003-08-06 0:42 Samuel Flory
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=3F3131D2.7050009@rackable.com \
--to=sflory@rackable.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
/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