From: Len Brown <len.brown@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: ACPI problem with latest 2.6 snapshot
Date: 24 Mar 2004 23:11:55 -0500 [thread overview]
Message-ID: <1080187915.21259.354.camel@dhcppc4> (raw)
In-Reply-To: <1080136312.2309.9.camel@pegasus>
Thanks for reporting this failure Marcel.
I expect we'll have this problem in 2.4.26 too.
On Wed, 2004-03-24 at 08:51, Marcel Holtmann wrote:
> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 22 low level)
rats, I don't have a non-identity SCI over-ride like this to test on.
> ACPI: Subsystem revision 20040311
> ACPI: SCI (IRQ22) allocation failed
> ACPI-0133: *** Error: Unable to install System Control Interrupt Handler, AE_NOT_ACQUIRED
> ACPI: Unable to start the ACPI Interpreter
apparently setting up IRQ22 on the IOAPIC early made it unavailable for
subsequent request_irq().
> ACPI: ACPI tables contain no PCI IRQ routing entries
> PCI: Invalid ACPI-PCI IRQ routing table
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
> PCI: Enabled i801 SMBus device
> Transparent bridge - 0000:00:1e.0
> PCI: Using IRQ router PIIX/ICH [8086/2440] at 0000:00:1f.0
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
Marcel,
I've dropped this info into a new bug report:
http://bugzilla.kernel.org/show_bug.cgi?id=2366
can you add yourself to the cc:, and attach the complete dmesg -s40000
from the failure (or a "debug" console capture). Would like to confirm
that IRQ22 got set up correctly in the IOAPIC.
There are two bugs here,
1. AE_NOT_ACQUIRED on non-identity mapped SCI over-ride -- new
2. boot failure on AE_NOT_ACQUIRED -- old
thanks,
-Len
next parent reply other threads:[~2004-03-25 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1080136312.2309.9.camel@pegasus>
2004-03-25 4:11 ` Len Brown [this message]
2004-03-25 14:24 ` ACPI problem with latest 2.6 snapshot Marcel Holtmann
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=1080187915.21259.354.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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