[Bug 207906] New: ACPI problem - Dell E1405 locks up when power cord is plugged in or removed
https://bugzilla.novell.com/show_bug.cgi?id=207906 Summary: ACPI problem - Dell E1405 locks up when power cord is plugged in or removed Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Mobile Devices AssignedTo: behlert@novell.com ReportedBy: jbarton@technicalworks.net QAContact: qa@suse.de I have recently purchased a Dell Inspiron E1405 with an Intel Core 2 Duo chipset and Im running openSuse 10.1 on it. My problem is that anytime I plug in the power cord or unplug the cord, the laptop freezes and I have to turn it off and reboot. I have tried running Gentoo on it and it gives the same problem, however the problem does not exist in either distribution under the 2.6.18 vanilla kernel sources. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 judas_iscariote@shorewall.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|Mobile Devices |Kernel Info Provider| |jbarton@technicalworks.net ------- Comment #1 from judas_iscariote@shorewall.net 2006-09-24 22:34 MST ------- this should be a kernel problem --> reclassificated. can u please provide the information requested here : http://en.opensuse.org/Bugs/Kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@novell.com AssignedTo|behlert@novell.com |trenn@novell.com Status|NEEDINFO |NEW Info Provider|jbarton@technicalworks.net | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jbarton@technicalworks.net -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 jbarton@technicalworks.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jbarton@technicalworks.net | ------- Comment #2 from jbarton@technicalworks.net 2006-09-25 09:54 MST ------- This is a hard lockup, so logging is available. I tried booting with the acpi=off parameter and the machine goes blank and does not boot. I also tried booting the "Failsafe" kernel and parameters installed by SuSE, and that freezes after "Booting the Kernel...." Under Gentoo (also on the machine), the same lockup happens under their default kernel unless I recompile it with ACPI support completely removed. Both distributions boot the vanilla 2.6.18 kernel with no problem. -John -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jbarton@technicalworks.net ------- Comment #3 from trenn@novell.com 2006-09-25 10:30 MST ------- Can you please attach: - dmesg output of the broken kernel (should work as long as you don't touch the AC plug?) - dmesg of a 2.6.18 working kernel - acpidump output of a 10.1 or 10.2 kernel, doesn't matter -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 jbarton@technicalworks.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED ------- Comment #4 from jbarton@technicalworks.net 2006-09-25 11:19 MST ------- Created an attachment (id=99577) --> (https://bugzilla.novell.com/attachment.cgi?id=99577&action=view) Dmesg Output from stock SuSE kernel ( broken kernel ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 ------- Comment #5 from jbarton@technicalworks.net 2006-09-25 11:19 MST ------- Created an attachment (id=99578) --> (https://bugzilla.novell.com/attachment.cgi?id=99578&action=view) Dmesg output from vanilla 2.6.18 kernel compile with config from suse kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 ------- Comment #6 from jbarton@technicalworks.net 2006-09-25 11:20 MST ------- Created an attachment (id=99579) --> (https://bugzilla.novell.com/attachment.cgi?id=99579&action=view) acpidump output under stock suse kernel -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jbarton@technicalworks.net ------- Comment #7 from trenn@novell.com 2006-10-30 05:52 MST ------- Sorry for not ansering... I missed that one.. That's strange, I only can see a lot differently assigned interrupts, but nothing especially related to AC. Is this problem reproducable all the time? E.g. the machine works reliable for a long time, only possiility to lock it up is unplugging AC, but this always locks the machine up? If this is an interrupt problem I expect it locks up on the first ACPI interrupt (e.g. lid opening/closing should produce one). In cat /proc/interrupts you should see a ACPI line. Does this one increase if you close and reopen the lid and the machine is still working. If this does not work, it's probably something with interrupts. If the machine still works, can you "rmmod ac" module and try to lock the machine up by unplugging AC. If it still locks, pls try also "rmmod battery" module. Sorry that I lost this one, I will keep track of it now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 jbarton@technicalworks.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jbarton@technicalworks.net | ------- Comment #8 from jbarton@technicalworks.net 2006-10-30 11:03 MST ------- Yes, this problem is repeatable every time, and the machine is rock solid with or without the AC plugged in, it is only the change from one state to another that causes lockup.. You are correct about opening / closing the lid, this also causes the laptop to lock up, no abililty to get to logs (In reply to comment #7)
Sorry for not ansering... I missed that one.. That's strange, I only can see a lot differently assigned interrupts, but nothing especially related to AC.
Is this problem reproducable all the time? E.g. the machine works reliable for a long time, only possiility to lock it up is unplugging AC, but this always locks the machine up?
If this is an interrupt problem I expect it locks up on the first ACPI interrupt (e.g. lid opening/closing should produce one). In cat /proc/interrupts you should see a ACPI line. Does this one increase if you close and reopen the lid and the machine is still working. If this does not work, it's probably something with interrupts.
If the machine still works, can you "rmmod ac" module and try to lock the machine up by unplugging AC. If it still locks, pls try also "rmmod battery" module.
Sorry that I lost this one, I will keep track of it now.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 novell@colin.guthr.ie changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell@colin.guthr.ie ------- Comment #9 from novell@colin.guthr.ie 2006-11-08 09:53 MST ------- I do not use Suse but I have a similar Core 2 Duo Dell laptop (Inspiron 6400 MM061). I had huge stability problems with booting with 2 cores enabled which is still causing me trouble (*lots* of NMI interupts recorded which is odd). I disabled one of the cores in BIOS and it works OK but I then have the exact problem you define (although I did still get some NMI's, tho' not as many) After some experimentation, I found I could reduce the NMI count to 0 by enabling both cores in BIOS (this was required) and passing the kernel option acpi=noirq. This had the effect of disabling one of the cores anyway but meant that I could happily shut the lid/remove power etc without lockup. FDO Bug https://bugs.freedesktop.org/show_bug.cgi?id=8776 tripped me up in that X11 would crash whenever I shut the lid (now fixed in Mandriva Cooker and upstream Xorg) and I still cannot get suspend to RAM working (could be related to the APCI cmd line param?). On the plus side Suspend To Disk works fine with a small tweak to re-run 915resolution on resume. (this is using the SWSUSP1 not suspend2 - not tried that!). Hope this info helps you get to the bottom of your problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |behlert@novell.com ------- Comment #10 from trenn@novell.com 2006-11-08 10:53 MST ------- Thanks for the detailed report. Stefan, I suggest this is rather critical and should at get fixed in SLE10 SP1 (10.2 is working, right?) Do we have such a machine and can we reproduce this here, I expect not? I don't have that much time currently, but try to come back to this one soon. I tried to get some input from Intel on that as it is already fixed, but no reply yet, I'll try again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|behlert@novell.com | ------- Comment #11 from behlert@novell.com 2006-11-30 06:04 MST ------- Thomas: Yes, we should fix this for SP1, and no, we don't have such a machine here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acpi@linux.intel.com ------- Comment #12 from trenn@novell.com 2006-12-12 11:10 MST ------- I agree, but touching interrupt routing code is potentially dangerous for a SP. As this is already fixed in mainline (probably and unfortunately before ACPICA patches got split up it's hard to find) we might have a chance to find some kind of small save fix up. As the dmesg of 2.6.16 kernel (non-working/freezing on first ACPI interrupt) and 2.6.18 (working kernel) show differences at which time which interrupt is assigned I expect this got fixed somewhere in ACPI interrupt code. If we'd had the machine here a bisec could help... Ohh, I just got a bug where SLES10 worked and for 10.2 pci=noacpi is needed. Just an idea..., but the fix that made the DELL work, could have broken the Siemens Esprimo P5615: bug #205417 Both these bugs are public, need some input from Intel or I'd say it's not worth searching. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207906#c13
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=207906#c14
Stephan Kulow
participants (1)
-
bugzilla_noreply＠novell.com