Bug 143943

Summary: Asus A6K laptop hangs when booting from batteries
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Stefan Kooman <sk>
Component: OtherAssignee: Stefan Behlert <behlert>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: sk
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: dmesg
hwinfo
tail -n 300 /var/log/messages

Description Stefan Kooman 2006-01-18 21:32:56 UTC
Asus A6K laptop hangs if it is booted from batteries. If it is booted while being hooked up to power supply the systems boots fine.
The systems hangs while initializing the second stage of the Suse Firewall.
Comment 1 Michael Gross 2006-01-19 13:18:18 UTC
Please provide more information: Provide /var/log/boot.msg as well as 300 lines of your syslog in /var/log/messages. Give more information about the hardware in use (`hwinfo') and attach it here. How long did you wait before you came to the conclusion that the system hangs? Does it really die (numlock no longer working, ...) or does it just stale? You can try pressing Ctrl-C here.
Comment 2 Michael Gross 2006-01-24 18:30:48 UTC
Please reopen this report if the information asked for can be provided.
Comment 3 Stefan Kooman 2006-02-02 19:08:00 UTC
Created attachment 66243 [details]
dmesg
Comment 4 Stefan Kooman 2006-02-02 19:08:37 UTC
Created attachment 66244 [details]
hwinfo
Comment 5 Stefan Kooman 2006-02-02 19:09:04 UTC
Created attachment 66245 [details]
tail -n 300 /var/log/messages
Comment 6 Stefan Kooman 2006-02-02 19:10:48 UTC
Provided additional information about system (hwinfo, demsg, tail on /var/log/messages)
Comment 7 Martin Lasarsch 2006-02-03 10:33:21 UTC
mobile-team: before assigning it to somebody else, any ideas?
Comment 8 Stefan Behlert 2006-02-13 09:48:34 UTC
This sounds strange. I would guess it is either a hardware-problem - or an ACPI problem, but hard to say.
Stefan: Does it boot if you deactivate the firewall?
Comment 9 Stefan Kooman 2006-02-14 19:00:14 UTC
I installed a new kernel (2.6.13-15.8-default) instead of linux-2.6.13-15.7. With the new kernel I don't have the problem anymore: with or without the firewall. Has anything changed in the kernel with respect to ACPI for Asus laptop or with the firewall?
Comment 10 Stefan Behlert 2006-02-21 13:13:28 UTC
Well, there has changed a little bit in the ACPI-code, but not from linux-2.6.13-15.7 to linux-2.6.13-15.8.
ACPI simply is strange. I'll close the bug, but please don't hesitate to reopen it when the problem occurs again. Thanks for testing the new kernel.
Comment 11 Stefan Kooman 2006-02-21 18:47:30 UTC
Problem has reoccured. System hanged again. I shutdown the firewall and rebooted but no change. When I replug the power and reboot the system it will hang the first time (with power attached) as well. A reboot after that and the system will just boot again. 
Comment 12 Stefan Behlert 2006-02-22 19:05:14 UTC
Stefan, the information appended in comment 3 and 5 is after the successful boot, isn't it?
Can you please do the following?
Remove /var/log/message, boot with power cord unplugged (which will fail, I hope), boot again with power cord plugged, and attach the /var/log/messages.
Although normally the 300 lines advice is sound it doesn't help in this case, unfortunately.
Comment 13 Stefan Behlert 2006-06-28 14:44:59 UTC
Stefan, could you reproduce the problem with a 10.1?
Comment 14 Stefan Kooman 2006-06-28 15:50:46 UTC
I have tested Opensuse 10.1 and could not reproduce the error (it does not occur).
At the moment I have installed gentoo (I got crazy from buggy zen package manager) so not able to do more testing anytime soon.
I recently installed FreeBSD 6.1 on the A6K and it hangs when it's not plugged in. I will file a bug report at FreeBSD. Maybe its related.
Comment 15 Stefan Behlert 2006-06-29 10:36:24 UTC
So it looks like we got it in one of the ACPI patches for 10.1.
(Hard to test without such a machine, so I do not think we will fix this for 10.0 - simply because we can not see what's fixing it:( )
Yes, it might be related, I think it is a problem in the ACPI code.