Bug 45451
Summary: | Suspend via s2ram fails on lid close after 24 hours uptime - Lenovo T420 | ||
---|---|---|---|
Product: | Power Management | Reporter: | athlion |
Component: | Hibernation/Suspend | Assignee: | power-management_other |
Status: | CLOSED UNREPRODUCIBLE | ||
Severity: | normal | CC: | alan, lenb, rui.zhang, zhenyu.z.wang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.3.8,3.4.7 ,3.5.0 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
athlion
2012-08-02 18:16:48 UTC
if instead of closing the lid and having arch linux invoke s2ram you directly echo mem > /sys/power/state -- does it work? Yes, it works flawlessly. Furthermore, I have traced where the kernel stops executing the suspend process: drivers/tty/vt/vt_ioctl.c:133: wait_event_interruptible drivers/tty/vt/vt_ioctl.c:1426: vt_waitactive kernel/power/console.c:19: vt_move_to_console kernel/power/suspend.c:98: pm_prepare_console suspend_prepare() called The call to wait_event_interruptible() never returns. Furthermore, my whole X session crashes on the failed suspend with this backtrace (I have also filed a bug under X.org): [ 13271.945] [ 13271.945] Backtrace: [ 13271.947] 0: /usr/bin/X (xorg_backtrace+0x36) [0x5602d6] [ 13271.947] 1: /usr/bin/X (0x400000+0x164039) [0x564039] [ 13271.948] 2: /usr/lib/libpthread.so.0 (0x7fe743ec1000+0xf170) [0x7fe743ed0170] [ 13271.948] 3: /usr/bin/X (XIChangeDeviceProperty+0x1b8) [0x502b88] [ 13271.948] 4: /usr/bin/X (DisableDevice+0x20f) [0x42d8ef] [ 13271.948] 5: /usr/bin/X (xf86Wakeup+0x494) [0x46fa54] [ 13271.948] 6: /usr/bin/X (WakeupHandler+0x6b) [0x43848b] [ 13271.948] 7: /usr/bin/X (WaitForSomething+0x1a4) [0x55d714] [ 13271.948] 8: /usr/bin/X (0x400000+0x34281) [0x434281] [ 13271.948] 9: /usr/bin/X (0x400000+0x23615) [0x423615] [ 13271.948] 10: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fe742d70725] [ 13271.949] 11: /usr/bin/X (0x400000+0x238ed) [0x4238ed] [ 13271.949] [ 13271.949] Segmentation fault at address 0x11 [ 13271.949] Fatal server error: [ 13271.949] Caught signal 11 (Segmentation fault). Server aborting [ 13271.949] [ 13271.949] Please consult the The X.Org Foundation support at http://wiki.x.org I strongly believe these two are related but I can't go one step further from there.... Ehm, sorry, I forgot to state that in the kernel backtrace, line numbers are against linux-3.4.9. The X.org bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=53593 zhenyu may have some thoughts on this. Zhenyu, can you take a look at this? It turns out that a faulty synaptics driver crashed during lid-close and brought the whole X server down with it so the kernel probably waited for something (from X) that never happened. Anyway, this is no longer happening, but I'll be happy to help if you think the kernel's behaviour was erratic nevertheless. Thanks! okay, first, it is a driver problem rather than a suspend/resume bug. second, it can not be reproduced any more. so I'll close this bug. please feel free to re-open it once it bothers you again. |