PROBLEM: ACPI freezes 2.6.1 on boot
Hi all,
I've seen the mail by Martin Loschwitz of January 1st 2004, in which he reported:
Quoted 8 lines
I'm writing this mail as I'm discovering ACPI related problems on my Acer TravelMate 800LCi notebook with Linux 2.6.1-rc1-mm1.
While the system boots up fine with Linux 2.6.1-rc1, with 2.6.1-rc1-mm1 it hangs while booting. The last message printed to screen is "ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd". This is fully reproducable with a Linux 2.6.0 kernel which has the ACPI20031203 patch applied.
I'm now seeing the _exact same problem_ on an ASUS M2400N [*] with a Linux 2.6.1 (unpatched) kernel. The kernel freezes after printing
"ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd"
(yes, the typo is in the kernel, it seems)
I've seen no reply to his mail. Has the problem been solved or is it still a known bug(tm)?
Martin? Were you successful in resolving that problem?
Regards,
Georg
[*] Pentium 4 M Centrino, 1.6, 512MB, Intel 855GM chipset
Signature · 3 lines
Georg C. F. Greve <[email protected]> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org)
Quoted 17 lines · Georg C. F. Greve
Hi all,
I've seen the mail by Martin Loschwitz of January 1st 2004, in which he reported:
Quoted 8 lines
I'm writing this mail as I'm discovering ACPI related problems on my Acer TravelMate 800LCi notebook with Linux 2.6.1-rc1-mm1.
While the system boots up fine with Linux 2.6.1-rc1, with 2.6.1-rc1-mm1 it hangs while booting. The last message printed to screen is "ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd". This is fully reproducable with a Linux 2.6.0 kernel which has the ACPI20031203 patch applied.
I'm now seeing the
_exactsameproblem_on an ASUS M2400N [*] with a Linux 2.6.1 (unpatched) kernel. The kernel freezes after printing
Quoted 9 lines
"ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd"
(yes, the typo is in the kernel, it seems)
I've seen no reply to his mail. Has the problem been solved or is it still a known bug(tm)?
Martin? Were you successful in resolving that problem?
By now means. I, however, didn't even try to get a solution since back then. Since the bug appeared with a patched 2.6.0 and 2.6.1-mm2, which was one of the first patches including the new ACPI, it was clear to me that it was ACPI related and that I would better wait for somebody to find the root of the evil and to kill it.
I see your "Notebook vs. Linux"-story continues to be unsuccessfull, though :(
Quoted 10 lines
Regards,
Georg[*] Pentium 4 M Centrino, 1.6, 512MB, Intel 855GM chipset
Signature · 3 lines
Georg C. F. Greve <[email protected]> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org)
Signature · 4 lines
.''`. Martin Loschwitz Debian GNU/Linux developer : :' : [email protected] [email protected] `. `'` http://www.madkiss.org/ people.debian.org/~madkiss/ `- Use Debian GNU/Linux 3.0! See http://www.debian.org/
|| On Wed, 21 Jan 2004 16:35:51 +0100 || Martin Loschwitz <[email protected]> wrote:
ml> By now means. I, however, didn't even try to get a solution since ml> back then. Since the bug appeared with a patched 2.6.0 and ml> 2.6.1-mm2, which was one of the first patches including the new ml> ACPI, it was clear to me that it was ACPI related and that I ml> would better wait for somebody to find the root of the evil and ml> to kill it.
Damn. ACPI being somewhat a central issue, I hoped someone had picked it up already. Did you write to the ACPI list about it? My mail apparently didn't make it (couldn't see it in the archive).
ml> I see your "Notebook vs. Linux"-story continues to be ml> unsuccessfull, though :(
Yup, it seems that way. It is an eternal struggle. *sigh*
Nice to see that someone read the issue, though. :)
Regards,
Georg
Signature · 3 lines
Georg C. F. Greve <[email protected]> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org)
Quoted 5 lines · Georg C. F. Greve
I'm now seeing the
_exactsameproblem_on an ASUS M2400N [*] with a Linux 2.6.1 (unpatched) kernel. The kernel freezes after printing"ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd"
Does it go away if you just make "acpi_pic_set_level_irq()" do nothing (ie just remove the "outb()" call
arch/i386/kernel/acpi/boot.c line 273
or just make the if-statement be always false).
It's entirely possible that the SCI is just horribly broken, and can't be level-triggered.
Btw, usually a good idea to at least cc the developer list for the
particular subsystem. In this case <[email protected]>. Many people don't have the time to follow linux-kernel.
Linus
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
Quoted 9 lines · Linus Torvalds
Does it go away if you just make "
acpi_pic_set_level_irq()" do nothing (ie just remove the "outb()" callarch/i386/kernel/acpi/boot.c line 273or just make the if-statement be always false).
It's entirely possible that the SCI is just horribly broken, and can't be level-triggered.
Just tried removing the outb() call both from plain vanilla 2.6.1 and one with the latest ACPI patch. No change. The system freezes with the same message at the same point during bootup.
Any other ideas?
Regards,
Georg
Signature · 10 lines
Georg C. F. Greve <greve-mXXj517/[email protected]> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org) ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn
And disable apic (lopic and io-pic) options from kernel compilation ?
Quoted 20 lines · Georg C. F. Greve
Quoted 9 lines · Linus Torvalds
Does it go away if you just make "
acpi_pic_set_level_irq()" do nothing (ie just remove the "outb()" callarch/i386/kernel/acpi/boot.c line 273or just make the if-statement be always false).
It's entirely possible that the SCI is just horribly broken, and can't be level-triggered.
Just tried removing the
outb()call both from plain vanilla 2.6.1 and one with the latest ACPI patch. No change. The system freezes with the same message at the same point during bootup.Any other ideas?
Regards,
Georg
Signature · 10 lines
Sérgio M B ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn
|| On 21 Jan 2004 21:51:27 +0000 || Sérgio Monteiro Basto <[email protected]> wrote:
smb> And disable apic (lopic and io-pic) options from kernel compilation ?
Funny -- we seemed to have had the same idea.
Yes, this makes it boot (see my other mail).
Regards,
Georg
Signature · 10 lines
Georg C. F. Greve <greve-mXXj517/[email protected]> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org) ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn
So you are another APIC victim :)
The funny thing, is that I thought that because,
Linus has write :
"It's entirely possible that the SCI is just horribly broken, and can't be level-triggered" about "ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd".
And thinking, can be true ? that, if SCI can't be level-triggered (like my laptop and yours), kernel with APIC (loapic or smp) options will hang on boot !
Quoted 16 lines · Georg C. F. Greve
|| On 21 Jan 2004 21:51:27 +0000 || Sérgio Monteiro Basto <[email protected]> wrote:smb> And disable apic (lopic and io-pic) options from kernel compilation ?
Funny -- we seemed to have had the same idea.
Yes, this makes it boot (see my other mail).
Regards,
GeorgSignature · 3 lines
Georg C. F. Greve <greve-mXXj517/[email protected]> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org)
Signature · 10 lines
Sérgio M B ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn
|| On 21 Jan 2004 23:31:43 +0000 || Sérgio Monteiro Basto <[email protected]> wrote:
smb> So you are another APIC victim :)
Seems that way. :)
smb> [...]
smb> And thinking, can be true ? that, if SCI can't be smb> level-triggered (like my laptop and yours), kernel with APIC smb> (loapic or smp) options will hang on boot !
But can it really not be level triggered?
My dmesg output tells me explicitly that it switched to level triggered successfully when APIC is disabled.
So is that message wrong or is there a problem between APIC/ACPI?
Should we not be able to resolve that problem anytime soon, I would suggest to add some information about this to the Kernel help for both ACPI and APIC, like:
"
CAUTION:
On some laptops, enabling both local APIC and ACPI can cause problems. Should your system hang during boot with a message like
'ACPI: IRQ X was Edge Triggered, setting to Level Triggerd'
you should disable either local APIC (recommended) or ACPI. See http://bugzilla.kernel.org/show_bug.cgi?id=1774 for details.
"
that could save people a lot of time in the future hunting down that bug again -- also it should limit the amount of mails sent around on the topic. :)
Regards,
Georg
Signature · 10 lines
Georg C. F. Greve <greve-mXXj517/[email protected]> Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org) ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn
Quoted 6 lines · Georg C. F. Greve
Just tried removing the
outb()call both from plain vanilla 2.6.1 and one with the latest ACPI patch. No change. The system freezes with the same message at the same point during bootup.Any other ideas?
Nope. It would probably help to enable ACPI debugging, and see if there are any other messages printed.
And it would also help to go back to the working kernel (somebody said 2.6.1-rc1 worked), and try to see what the differences are and what is the first kernel that breaks. -rc2? -rc3? or 2.6.1-final?
Linus
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn