|
Bugzilla – Full Text Bug Listing |
| Summary: | s2ram on lid close only every second time | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Christian Trippe <ctrippe> |
| Component: | Kernel | Assignee: | Thomas Renninger <trenn> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | trenn |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Trippe
2007-11-10 18:49:47 UTC
I'm not sure if this is a kernel problem. Can you do root@amd:~# cat /proc/acpi/event ibm/hotkey HKEY 00000080 00005001 button/lid LID 00000080 00000001 ibm/hotkey HKEY 00000080 00005002 button/lid LID 00000080 00000002 (you'll need to kill acpid or something), verify it works for you, then suspend/resume and see how it interacts? Also verify: root@amd:~# cat /proc/acpi/button/lid/LID/* type: Lid Switch state: open After stopping acpid "cat /proc/acpi/event" returns nothing. The other thing you asked for is true: cat /proc/acpi/button/lid/LID0/* type: Lid Switch state: open Doing the suspend/resume. The value of "cat /proc/acpi/button/lid/LID0/*" does not change. cat /proc/acpi/event button/lid LID0 00000080 00000003 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 processor CPU0 00000081 00000000 Doing another lid-close where it does not suspend button/lid LID0 00000080 00000001 button/lid LID0 00000080 00000002 is added to the output of /proc/acpi/event Does this still happen with latest 10.3 update kernel? If yes, pls carefully check: - Do acpi events for LID closing AND opening happen, this should look like: button/lid LID0 00000080 0000000X every time the LID is opened or closed. Can you verify that those events still show up after a suspend (better check some more events than one...). - Is the LID open/close status correct After suspending, check for: cat /proc/acpi/button/lid/LID0/* Is the status correct? Open and close the Lid some times and recheck, do you get into a state where it is not correct? It still happens with the latest kernel: uname -r 2.6.22.13-0.3-default After a fresh boot I have: cat /proc/acpi/button/lid/LID0/* type: Lid Switch state: open This result is always the same. 1.)Doing the first lid close the notebook does s2ram. After opening the lid and pressing the power-button it resumes. Output of acpi_listen: button/lid LID0 00000080 00000001 The result of "cat /proc/acpi/button/lid/LID0/*" stays the same as above. 2.)The next lid close does not s2ram. Opening the LID again the sessions is not even locked. Output of acpi_listen: button/lid LID0 00000080 00000001 button/lid LID0 00000080 00000002 "cat /proc/acpi/button/lid/LID0/*" gives the same as above. 3.)The next lid close the notebook does s2ram. After opening the lid and pressing the power-button it resumes. Output of acpi_listen: button/lid LID0 00000080 00000003 "cat /proc/acpi/button/lid/LID0/*" gives the same as above. From now on 2.) and 3.) are repeated. Can you try one of these kernels, pls: ftp.suse.com/pub/people/trenn/s2ram_lid_issue (In reply to comment #6 from Thomas Renninger) > Can you try one of these kernels, pls: > ftp.suse.com/pub/people/trenn/s2ram_lid_issue > I installed kernel-default-2.6.22.15-0.3.i586.rpm. The behaviour is changed but worse as a lid-close does now never result in s2ram. The output of cat /proc/acpi/button/lid/LID0/* type: Lid Switch state: open is always the same. acpi_listen gives button/lid LID0 00000080 00000002 button/lid LID0 00000080 00000003 for the first lid-close/lid-open after a fresh boot the second gives button/lid LID0 00000080 00000004 button/lid LID0 00000080 00000005 and so on. > The behaviour is changed but worse as a lid-close does now never result in
> s2ram.
Ok, we should better move this on to 11.0.
I don't want to take the risk to break other machines.
Please try the next 11.0 Alpha/Beta release.
If you still have problems there, we still have enough time to fix it and sent patches upstream for broad testing.
You may then want to reopen the bug instead of creating a new one and adjust the product from 10.3 to 11.0
Hello Thomas, I did what you suggested and installed 11.0 Alpha2. There it works fine. The machine suspends with every lid-close. I do not know if should move the bug to 11.0 and close it as fixed? Thanks again for your help. Christian No, better let it as it is. People also running into this have a reference with this bug report now. Thanks for trying out. |