[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 <axboe@kernel.dk> 2007-09-20 08:01:26 MST --- Additional note: the inferior x60s uses the SUSE kernels but I use home brew kernels, so it's likely not a kernel issue. It's not a basesystem bug either, but I didn't quite find an appropriate section. -- 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 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |seife@novell.com -- 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#c2 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fseidel@novell.com, hmacht@novell.com, | |dkukawka@novell.com Status|NEW |ASSIGNED --- Comment #2 from Stefan Seyfried <seife@novell.com> 2007-09-20 17:47:31 MST --- It might be either a HAL or a kpowersave issue (assuming you are using KDE). Please, before the first lid close, start a "lshal -m" and watch out for something like this: 01:46:58.961: computer_logicaldev_input_0 property button.state.value = true 01:46:58.963: computer_logicaldev_input_0 condition ButtonPressed = lid when closing the lid. -- 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#c3 --- Comment #3 from Jens Axboe <axboe@kernel.dk> 2007-09-21 03:03:12 MST --- Stefan, I am using KDE. So I did what you described and closed the lid: axboe@carl:~> lshal -m Start monitoring devicelist: ------------------------------------------------- 10:58:51.372: computer_logicaldev_input_3 property button.state.value = false 10:58:51.374: computer_logicaldev_input_3 condition ButtonPressed = lid After lid close, the machine did not suspend and I opened it again. The above is what got generated. Then I closed the lid again, this time it suspended. Opening and resuming, the following three lines appeared: 11:00:18.232: computer_logicaldev_input_3 property button.state.value = true 11:00:18.236: computer_logicaldev_input_3 condition ButtonPressed = lid 11:00:28.681: acpi_BAT0 property battery.voltage.current = 16679 (0x4127) -- 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#c4 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com AssignedTo|seife@novell.com |dkukawka@novell.com Status|ASSIGNED |NEW --- Comment #4 from Stefan Seyfried <seife@novell.com> 2007-09-24 01:34:06 MST --- in this case, i suspect this to be a kpowersave 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.
https://bugzilla.novell.com/show_bug.cgi?id=326814#c5 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |axboe@kernel.dk --- Comment #5 from Danny Kukawka <dkukawka@novell.com> 2007-09-24 05:21:54 MST --- The problem is not KPowersave at it looks to me. The first output show only the open of the lid (button.state.value = false means the lid was opened). Looks as if some events get lost. Could you do this: - disable 'lock screen on suspend' in the KPowersave settings - start 'lshal -m', acpi_listen and 'while true; do date; cat /proc/acpi/button/lid/LID/* ;sleep 1; done' - close the lid - open the lid - post the outputs -- 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#c6 --- Comment #6 from Jens Axboe <axboe@kernel.dk> 2007-09-24 06:16:44 MST --- Alright, I did what you described. First I closed the lid where it didn't do anything, this is the output: lshal -m 14:10:19.022: computer_logicaldev_input_3 property button.state.value = false 14:10:19.024: computer_logicaldev_input_3 condition ButtonPressed = lid acpi_listen button/lid LID 00000080 00000005 button/lid LID 00000080 00000006 while true; do date; cat /proc/acpi/button/lid/LID/*; sleep 1; done Mon Sep 24 14:10:11 CEST 2007 type: Lid Switch state: open Mon Sep 24 14:10:12 CEST 2007 type: Lid Switch state: open Mon Sep 24 14:10:13 CEST 2007 type: Lid Switch state: closed Mon Sep 24 14:10:14 CEST 2007 type: Lid Switch state: closed Mon Sep 24 14:10:15 CEST 2007 type: Lid Switch state: closed Mon Sep 24 14:10:16 CEST 2007 type: Lid Switch state: closed Mon Sep 24 14:10:17 CEST 2007 type: Lid Switch state: closed Mon Sep 24 14:10:18 CEST 2007 type: Lid Switch state: open Mon Sep 24 14:10:19 CEST 2007 type: Lid Switch state: open And then I closed it again, this time it suspended fine. Output on the xterms after resume: lshal -m 14:11:27.028: computer_logicaldev_input_3 property button.state.value = true 14:11:27.030: computer_logicaldev_input_3 condition ButtonPressed = lid acpi_listen. button/lid LID 00000080 00000007 processor CPU0 00000081 00000000 processor CPU1 00000081 00000000 while true; do date; cat /proc/acpi/button/lid/LID/*; sleep 1; done Mon Sep 24 14:11:25 CEST 2007 type: Lid Switch state: open Mon Sep 24 14:11:27 CEST 2007 type: Lid Switch state: open Mon Sep 24 14:11:28 CEST 2007 type: Lid Switch state: closed Mon Sep 24 14:11:37 CEST 2007 type: Lid Switch state: open Mon Sep 24 14:11:38 CEST 2007 type: Lid Switch state: open Mon Sep 24 14:11:39 CEST 2007 type: Lid Switch state: open -- 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#c7 --- Comment #7 from Danny Kukawka <dkukawka@novell.com> 2007-09-24 06:40:40 MST --- Could you attach output of lshal on a fresh booted system? Looks to me as if the first event get lost or wrong read from /proc or /sys. Could you may also test from console what lshal print if you close the lid (check if there is any lid related output before open the lid 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.
https://bugzilla.novell.com/show_bug.cgi?id=326814#c9 Adam Martinson <loki1984@vfemail.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|axboe@kernel.dk | --- Comment #9 from Adam Martinson <loki1984@vfemail.net> 2007-10-08 16:14:32 MST --- Created an attachment (id=176916) --> (https://bugzilla.novell.com/attachment.cgi?id=176916) lshal output on a freshly booted system -- 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#c10 --- Comment #10 from Adam Martinson <loki1984@vfemail.net> 2007-10-08 16:16:08 MST --- Created an attachment (id=176917) --> (https://bugzilla.novell.com/attachment.cgi?id=176917) lshal output after lid close, suspend-to-ram, lid open, and resume -- 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#c11 Adam Martinson <loki1984@vfemail.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |loki1984@vfemail.net --- Comment #11 from Adam Martinson <loki1984@vfemail.net> 2007-10-08 16:56:46 MST --- I attached lshal outputs for a freshly booted system (lshal.txt) and after lid close, suspend-to-ram, lid open, and resume (lshal2.txt). diff lshal.txt lshal2.txt produces: 119c119 < battery.alarm.design = 3240 (0xca8) (int) ---
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 <christiandehne@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christiandehne@web.de --- Comment #12 from Christian Trippe <christiandehne@web.de> 2007-10-09 01:47:17 MST --- For me bug #329628 seems to be a duplicate of this bug and shows that also other laptops are affected (and that the error is still present in GM). -- 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#c13 Christian Trippe <christiandehne@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvzwieten@vxcompany.com --- Comment #13 from Christian Trippe <christiandehne@web.de> 2007-10-09 01:49:11 MST --- *** Bug 329628 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=329628 -- 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#c14 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |loki1984@vfemail.net --- Comment #14 from Danny Kukawka <dkukawka@novell.com> 2007-10-09 03:29:17 MST --- (In reply to comment #11 from Adam Martinson)
< 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 <loki1984@vfemail.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|loki1984@vfemail.net | --- Comment #16 from Adam Martinson <loki1984@vfemail.net> 2007-10-15 11:21:08 MST --- Yes, the first output is from the successful case. Whether successful or unsuccessful cat /proc/acpi/button/lid/LID/* returns: type: Lid Switch state: open This is the output from evtest /dev/input/event4 for first a successful then an unsuccessful case: Input driver version is 1.0.0 Input device ID: bus 0x19 vendor 0x0 product 0x5 version 0x0 Input device name: "Lid Switch" Supported events: Event type 0 (Sync) Event type 5 (?) Event code 0 (?) Testing ... (interrupt to exit) Event: time 1192468547.780536, type 5 (?), code 0 (?), value 1 Event: time 1192468547.780542, -------------- Report Sync ------------ Event: time 1192468580.945090, type 5 (?), code 0 (?), value 0 Event: time 1192468580.945096, -------------- Report Sync ------------ Note that the last 2 lines are from the unsuccessful case. ~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#c17 --- Comment #17 from Adam Martinson <loki1984@vfemail.net> 2007-10-15 11:24:02 MST --- FYI the output from cat /proc/acpi/button/lid/LID/* is after closing & openning the lid. ~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#c18 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dkukawka@novell.com |kernel-maintainers@forge.provo.novell.com Severity|Major |Critical Component|Basesystem |Kernel Version|RC 1 |Final --- Comment #18 from Danny Kukawka <dkukawka@novell.com> 2007-10-16 16:02:36 MST --- This all looks to me like a ACPI kernel problem with lose a LID event. I reassign this to our kernel guys. -- 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 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.provo.novell.com |astarikovskiy@novell.com -- 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#c19 --- Comment #19 from Alexey Starikovskiy <astarikovskiy@novell.com> 2007-10-17 14:15:28 MST --- I think this a result of ACPI fighting with killing wake event and never letting it to appear in user space. Originally problem was that power/sleep button used for system wake-up got propagated to user space causing one more power-off/sleep. So, ACPI now kills wake event, and if it was lid-open event, it never reaches user space. -- 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#c20 --- Comment #20 from Alexey Starikovskiy <astarikovskiy@novell.com> 2007-10-18 06:27:05 MST --- Created an attachment (id=179226) --> (https://bugzilla.novell.com/attachment.cgi?id=179226) Send input event if lid state has changed during suspend/resume. Please check if such patch helps. -- 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#c21 --- Comment #21 from Jens Axboe <axboe@kernel.dk> 2007-10-18 08:05:12 MST --- Sorry for the lack of response here lately... Will try the patch, compiling yields: drivers/acpi/button.c: In function 'acpi_button_resume': drivers/acpi/button.c:356: error: 'struct input_dev' has no member named 'state' make[2]: *** [drivers/acpi/button.o] Error 1 make[1]: *** [drivers/acpi] Error 2 make: *** [drivers] Error 2 axboe@carl:~/git/linux-2.6-block> Seems it doesn't like current -git. Can I talk you into updating it, then I can try it right away. Otherwise I wont get to this until next week, I'm afraid. -- 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#c22 Alexey Starikovskiy <astarikovskiy@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #179226|0 |1 is obsolete| | --- Comment #22 from Alexey Starikovskiy <astarikovskiy@novell.com> 2007-10-18 14:45:34 MST --- Created an attachment (id=179336) --> (https://bugzilla.novell.com/attachment.cgi?id=179336) Send input event if lid state has changed during suspend/resume. input layer checks for redundant event itself... This patch should apply to current -git. -- 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#c23 Alexey Starikovskiy <astarikovskiy@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #179336|0 |1 is obsolete| | --- Comment #23 from Alexey Starikovskiy <astarikovskiy@novell.com> 2007-10-19 11:23:13 MST --- Created an attachment (id=179490) --> (https://bugzilla.novell.com/attachment.cgi?id=179490) Send switch event on LID init and resume. IMHO, resume is not the only place missing LID switch update, init time also should set state of input layer. -- 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 Alexey Starikovskiy <astarikovskiy@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |axboe@kernel.dk -- 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#c24 --- Comment #24 from Jens Axboe <axboe@kernel.dk> 2007-10-21 00:38:01 MST --- Alexey, I think this patch works! Of course I now run into ANOTHER bug that seems to happen for every 2nd boot, in that it prints 'Suspend to ram disabled by administrator' when I close the lid. But it does that on every close now, so it seems to catch the events at least. I will try a reboot now and verify it really does suspend every time. -- 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#c25 Jens Axboe <axboe@kernel.dk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|axboe@kernel.dk | --- Comment #25 from Jens Axboe <axboe@kernel.dk> 2007-10-21 00:49:04 MST --- OK, after two reboots (the first still displayed the perhaps even more annoying bug of 'Suspend to ram disabled by administrator') I can now confirm that the patch solves the issue. I've done 4 consecutive suspend and resumes with as many lid closes, perfect! So this bug can be closed. If anyone has hints as to the oft disabled STR, then please do let me know. -- 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#c26 --- Comment #26 from Danny Kukawka <dkukawka@novell.com> 2007-10-22 01:25:03 MST --- @Jens: the problems with the denied STR are IMO caused by bug #333735. Please try to test the solution in comment #12 there. -- 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#c27 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #27 from Thomas Renninger <trenn@novell.com> 2007-10-22 02:05:04 MST --- Patch from comment #23 added to SL103_BRANCH kernel branch. -- 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#c28 --- Comment #28 from Jens Axboe <axboe@kernel.dk> 2007-10-23 04:01:28 MST --- Danny, thanks will look at that bug. Thomas, I trust you will get this patch upstream as well? -- 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#c29 --- Comment #29 from Thomas Renninger <trenn@novell.com> 2007-10-23 07:09:23 MST --- AFAIK there already is a lid switch patch in mainline. I objected to it, as the real cause for this report was GPE's not enabled before _WAK (at least he reported it working with this one added and it's also in our kernel...), but I remember that Len has added both. -- 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#c30 --- Comment #30 from Jens Axboe <axboe@kernel.dk> 2007-10-23 07:16:39 MST --- But mainline does not work, unless you add the patch from comment #23. So whatever is in there isn't sufficient. -- 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#c31 --- Comment #31 from Thomas Renninger <trenn@novell.com> 2007-10-23 08:43:06 MST --- Ahh, and the problem was the missing event after suspend, not before. Alexey already sent it and got his first signed-off, should pop up there soon. -- 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#c32 --- Comment #32 from Jens Axboe <axboe@kernel.dk> 2007-10-24 03:28:11 MST --- Perfect, thanks a lot! -- 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#c33 --- Comment #33 from Len Brown <len.brown@intel.com> 2007-10-30 12:41:46 MST --- 23de5d9ef2a4bbc4f733f58311bcb7cf6239c813 (ACPI: button: send initial lid state after add and resume) shipped in Linux-2.6.24-rc1-git6 -- 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#c34 --- Comment #34 from Fred van Zwieten <fvzwieten@vxcompany.com> 2007-10-31 12:50:16 MST --- So, how do I get this bug resolved on my 10.3 install? Does this mean the bug is resolved in kernel 2.6.24-rc1-git6 and up? Great, but will it also get patched in tho 10.3 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.
https://bugzilla.novell.com/show_bug.cgi?id=326814#c35 --- Comment #35 from Thomas Renninger <trenn@novell.com> 2007-11-01 11:52:33 MST --- 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/ -- 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#c36 --- Comment #36 from Christian Trippe <christiandehne@web.de> 2007-11-05 03:02:55 MST --- (In reply to comment #35 from Thomas Renninger)
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 <christiandehne@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #37 from Christian Trippe <christiandehne@web.de> 2007-11-10 01:06:44 MST --- I installed the newest kernel-update (2.6.22.12-0.1-default) and still have the same problem. I again read the comments in this bug and found maybe a little difference to the original reporter. If I understand comment #3 correctly his notebook resumes on lid-open. For me this is different, I have to press the power-button to resume. So I reopen this bug. If you think this should be handled in another bug close this one again and I will report this as a new 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#c38 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #38 from Thomas Renninger <trenn@novell.com> 2007-11-10 10:56:41 MST --- Christian: Pls reopen your original bug. 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. Pls add me to CC of the other bug then. -- 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#c39 --- Comment #39 from Christian Trippe <christiandehne@web.de> 2007-11-10 12:30:06 MST --- (In reply to comment #38 from Thomas Renninger)
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