Kernel Bug Tracker – Bug 1677
boot hang: "ACPI: IRQ9 SCI: Level Trigger" - ATI
Last modified: 2004-08-13 19:37:56 UTC
Distribution: Gentoo Linux
Hardware Environment: Laptop HP Pavilion ze4430us
Problem Description: Kernel hangs with message "ACPI: IRQ9 SCI: Level Trigger".
Only bootable if acpi=off is passed as option. I applied the latest patch
available (acpi-20031203-2.6.0-test11.diff.bz2) with the same results.
I tried pci=noacpi and noapic also, no luck.
Also tried 2.6.0.test10-mm1, same thing.
Created attachment 1660 [details]
dmesg -s40000 (acpi=off)
Created attachment 1661 [details]
Created attachment 1662 [details]
Created attachment 1663 [details]
Created attachment 1664 [details]
try acpi_pic_sci=level, please
Does it still fail if you boot with pci=noacpi?
> ACPI: IRQ9 SCI: Level Trigger
This means that the kernel found IRQ 9 already set to level triggered,
so "acpi_pic_sci=level" should not have any effect. (acpi_pic_sci=edge may effect
the problem, but there is no indication that it is the right thing to do)
Seems more like we're getting some sort of event before we're ready -- should
be able to confirm by enabling debugging output.
Created attachment 1667 [details]
patch to enable verbose3 messages
Please apply this patch to enable verbose debugging and report the last thing
it prints before the hang.
I am currently compiling KDE so currently I can't give you results for the tests
I can add one thing: ACPI works if I disable Local APIC support on uniprocessors
and IO-APIC support on uniprocessors on a test11 kernel (unpatched).
I'll come back when KDE finishes so I can send your test results.
I patched the kernel as you asked but I get no debug messages. I am using the
plain test11 source (I didn't apply the latest patch available at SF) and I
don't get that SCI message anymore. Now all I get is "spurious 8259A interrupt:
IRQ7." right after "ACPI: Subsystem revision 20031002" and it hangs.
That "acpi_pic_sci=level" didn't change anything. Also pci=noacpi produces the
I'll try to get a serial console so I can put the entries here.
? Fixed there...
please re-open if the patch in bug #1269 does not address the problem.
*** This bug has been marked as a duplicate of 1269 ***
Yes, the patch in bug #1269 solved the problem. Now running 2.6.1 with APIC and