[Bug 326814] New: Laptop lid close doesn't always supend-to-ram
https://bugzilla.novell.com/show_bug.cgi?id=326814 Summary: Laptop lid close doesn't always supend-to-ram Product: openSUSE 10.3 Version: RC 1 Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: axboe@kernel.dk QAContact: qa@suse.de CC: thomas@kenne.dk Found By: --- My laptop is a Lenovo x60, and I always just close the lid to suspend-to-ram. With the newer 10.3 builds (as of current today), the first close never does anything. I have to reopen the laptop and close it again, then it suspends just fine. It seems like the first lid close doesn't generate an event. A friend of mine has an almost identical model (x60s), and it has the exact same symptoms. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=326814#c1
--- Comment #1 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=326814#c2
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=326814#c3
--- Comment #3 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c4
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=326814#c5
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=326814#c6
--- Comment #6 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c7
--- Comment #7 from Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=326814#c9
Adam Martinson
https://bugzilla.novell.com/show_bug.cgi?id=326814#c10
--- Comment #10 from Adam Martinson
https://bugzilla.novell.com/show_bug.cgi?id=326814#c11
Adam Martinson
battery.alarm.design = 5827 (0x16c3) (int) 151c151 < battery.voltage.current = 16749 (0x416d) (int)
battery.voltage.current = 16725 (0x4155) (int) 202c202 < button.state.value = false (bool)
button.state.value = true (bool)
The last part I think is the relevant one. After lid close, suspend-to-ram, lid open, and resume, the button.state.value for the lid doesn't get set back to false. After this auto-suspend on lid close fails. Manually initiating suspend-to-ram, and then closing the lid works, and it will automatically resume when you open the lid again, and afterward it will suspend when you close the lid (once). Either that or I can close the lid, open it, and close it again, and then it will work. So for me auto-suspend on lid close works every other time. I don't think it's a hal problem though, because using hal-set-property to manually change button.state.value back to false doesn't help! I really think this is an ACPI issue, because here's the output from acpi_listen during first a successful lid close->suspend->open->resume and then an unsuccessful one: ibm/hotkey HKEY 00000080 00005001 button/lid LID 00000080 00000007 processor CPU 00000081 00000000 ibm/hotkey HKEY 00000080 00005001 button/lid LID 00000080 00000008 ibm/hotkey HKEY 00000080 00005002 button/lid LID 00000080 00000009 After the successful one, the ACPI events for the lid opening are missing. ~Loki -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=326814#c12
Christian Trippe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c13
Christian Trippe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c14
Danny Kukawka
< button.state.value = false (bool) ---
button.state.value = true (bool)
The last part I think is the relevant one. After lid close, suspend-to-ram, lid open, and resume, the button.state.value for the lid doesn't get set back to false.
What was the output of cat '/proc/acpi/button/lid/LID/*' in this case?
I really think this is an ACPI issue, because here's the output from acpi_listen during first a successful lid close->suspend->open->resume and then an unsuccessful one: ibm/hotkey HKEY 00000080 00005001 button/lid LID 00000080 00000007 processor CPU 00000081 00000000
ibm/hotkey HKEY 00000080 00005001 button/lid LID 00000080 00000008 ibm/hotkey HKEY 00000080 00005002 button/lid LID 00000080 00000009
Are you sure the first output was from the successful case? I see there only one event for lid. I would assume the second one is the successfull case or not? Btw. Could you please install input-utils.rpm and do this: * evtest /dev/input/event4 (due to lshal this is the input device for the lid-switch on your machine, maybe there are the same problems with the input device of the lid as with acpi) * repoduce both cases (successful and unsuccessful case) * attach both outputs to the bug -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=326814#c16
Adam Martinson
https://bugzilla.novell.com/show_bug.cgi?id=326814#c17
--- Comment #17 from Adam Martinson
https://bugzilla.novell.com/show_bug.cgi?id=326814#c18
Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=326814
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=326814#c19
--- Comment #19 from Alexey Starikovskiy
https://bugzilla.novell.com/show_bug.cgi?id=326814#c20
--- Comment #20 from Alexey Starikovskiy
https://bugzilla.novell.com/show_bug.cgi?id=326814#c21
--- Comment #21 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c22
Alexey Starikovskiy
https://bugzilla.novell.com/show_bug.cgi?id=326814#c23
Alexey Starikovskiy
https://bugzilla.novell.com/show_bug.cgi?id=326814
Alexey Starikovskiy
https://bugzilla.novell.com/show_bug.cgi?id=326814#c24
--- Comment #24 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c25
Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c26
--- Comment #26 from Danny Kukawka
https://bugzilla.novell.com/show_bug.cgi?id=326814#c27
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=326814#c28
--- Comment #28 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c29
--- Comment #29 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=326814#c30
--- Comment #30 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c31
--- Comment #31 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=326814#c32
--- Comment #32 from Jens Axboe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c33
--- Comment #33 from Len Brown
https://bugzilla.novell.com/show_bug.cgi?id=326814#c34
--- Comment #34 from Fred van Zwieten
https://bugzilla.novell.com/show_bug.cgi?id=326814#c35
--- Comment #35 from Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=326814#c36
--- Comment #36 from Christian Trippe
See comment #23. Either wait for the next kernel update or get a kernel rpm from: ftp://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH/
I installed the kernel from this directory, but the bug is not resolved for me. My P35 suspends only every second lid-close. Kernel: 2.6.22.10-SL103_BRANCH_20071030153243-default -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=326814#c37
Christian Trippe
https://bugzilla.novell.com/show_bug.cgi?id=326814#c38
Thomas Renninger
https://bugzilla.novell.com/show_bug.cgi?id=326814#c39
--- Comment #39 from Christian Trippe
Christian: Pls reopen your original bug.
I have opened a new bug 340884, as the one marked as duplicate was also not reported by me.
If you still have problems, then the bug was already wrongly marked as duplicate of this one (no offence, it very much looked like a duplicate...). The problem of this bug is solved, mixing up things only ends in a totally confusing bug, with no help for others that might search the bugzilla database.
I understand this, I just did not know hot to proceed. -- 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.
participants (1)
-
bugzilla_noreply@novell.com