[solved] precious suspend doesn't work anymore!!!

DonVla · 2008-04-02 12:49:29

hello forum,

since two or three days (i think it has smth to do with the new 2.6.24.4-1 kernel upgrade) the s2disk and pm-hibernate command stopped to work.
when i try to supend it starts to suspend, but then after some seconds it returns to X. the kernel.log is full of such entries:

.
.
.
firefox-bin D c03850d4 0 4654 4071 │
Ap│Apr 2 14:39:06 kernel: ed1501c0 00000086 00000246 c03850d4 00000c00 00000001 ee9d9208 00000202 │
Ap│Apr 2 14:39:06 kernel: ed1501c0 c04a5080 00000001 c0127071 efa0d000 ec8b4ff0 ec8b5128 00000000 │
Ap│Apr 2 14:39:06 kernel: ec89be68 ec89be70 ec89be70 00000001 00000000 ec89beb4 ec89beb4 c055d538 │
Ap│Apr 2 14:39:06 kernel: Call Trace: │
Ap│Apr 2 14:39:06 kernel: [<c03850d4>] __mutex_lock_slowpath+0x234/0x2e0 │
Ap│Apr 2 14:39:06 kernel: [<c0127071>] __wake_up_sync+0x41/0x80 │
Ap│Apr 2 14:39:06 kernel: [<c01585fd>] refrigerator+0xad/0x100 │
Ap│Apr 2 14:39:06 kernel: [<c013ca3d>] get_signal_to_deliver+0x39d/0x4c0 │
Ap│Apr 2 14:39:06 kernel: [<c0128a70>] default_wake_function+0x0/0x10 │
00│Apr 2 14:39:06 kernel: [<c0104816>] do_notify_resume+0xc6/0x730 │45
Ap│Apr 2 14:39:06 kernel: [<c01441b0>] autoremove_wake_function+0x0/0x50 │
Ap│Apr 2 14:39:06 kernel: [<c01520f8>] sys_futex+0x98/0x120 │
Ap│Apr 2 14:39:06 kernel: [<c018996f>] sys_write+0x6f/0x80 │
Ap│Apr 2 14:39:06 kernel: [<c01056ce>] work_notifysig+0x13/0x19 │
Ap│Apr 2 14:39:06 kernel: ======================= │
Ap│Apr 2 14:39:06 kernel: firefox-bin D c160c2d4 0 8549 4071 │
Ap│Apr 2 14:39:06 kernel: ed1501c0 00000086 c0128642 c160c2d4 eebbba90 eebba038 c04a9280 00000001 │
Ap│Apr 2 14:39:06 kernel: ed150000 c04a5080 00000000 00000000 00000000 eeab7540 eeab7678 00000000 │
Ap│Apr 2 14:39:06 kernel: c39a3e68 c39a3e70 c39a3e70 00000001 00000000 c39a3eb4 c39a3eb4 c055e150 │
Ap│Apr 2 14:39:06 kernel: Call Trace: │
Ap│Apr 2 14:39:06 kernel: [<c0128642>] try_to_wake_up+0x52/0x480 │
Ap│Apr 2 14:39:06 kernel: [<c01585fd>] refrigerator+0xad/0x100 │
Ap│Apr 2 14:39:06 kernel: [<c013ca3d>] get_signal_to_deliver+0x39d/0x4c0 │
Ap│Apr 2 14:39:06 kernel: [<c0128a70>] default_wake_function+0x0/0x10 │
Ap│Apr 2 14:39:06 kernel: [<c0104816>] do_notify_resume+0xc6/0x730 │
Ap│Apr 2 14:39:06 kernel: [<c0187039>] filp_close+0x49/0x80 │
Ap│Apr 2 14:39:06 kernel: [<c01520f8>] sys_futex+0x98/0x120 │
Ap│Apr 2 14:39:06 kernel: [<c012a5cd>] finish_task_switch+0x1d/0xa0 │
01│Apr 2 14:39:06 kernel: [<c01056ce>] work_notifysig+0x13/0x19 │45
Ap│Apr 2 14:39:06 kernel: ======================= │
Ap│Apr 2 14:39:06 kernel: gconfd-2 D ef248d80 0 4121 1 │
Ap│Apr 2 14:39:06 kernel: ed150000 00000086 00000008 ef248d80 00000008 082c35f0 00001000 ef4f6394 │
Ap│Apr 2 14:39:06 kernel: eeaf5e00 c04a5080 c053be80 ef1dc000 00000000 eea96550 eea96688 00000000 │
Ap│Apr 2 14:39:06 kernel: c023eb38 eea96550 eea96550 eea969d4 00000000 c013c2f6 00000000 00000005 │
Ap│Apr 2 14:39:06 kernel: Call Trace: │
Ap│Apr 2 14:39:06 kernel: [<c023eb38>] elv_next_request+0xe8/0x1e0 │
Ap│Apr 2 14:39:06 kernel: [<c013c2f6>] dequeue_signal+0x86/0x170 │
Ap│Apr 2 14:39:06 kernel: [<c01585fd>] refrigerator+0xad/0x100 │
Ap│Apr 2 14:39:06 kernel: [<c013ca3d>] get_signal_to_deliver+0x39d/0x4c0 │
Ap│Apr 2 14:39:06 kernel: [<c0104816>] do_notify_resume+0xc6/0x730 │
Ap│Apr 2 14:39:06 kernel: [<c02c83eb>] scsi_end_request+0xbb/0xe0 │
Ap│Apr 2 14:39:06 kernel: [<c02c86f1>] scsi_io_completion+0xa1/0x3e0 │
Ap│Apr 2 14:39:06 kernel: [<c023f9a2>] blk_done_softirq+0x62/0x70 │
Ap│Apr 2 14:39:06 kernel: [<c013451a>] __do_softirq+0x8a/0x110 │
Ap│Apr 2 14:39:06 kernel: [<c0149daa>] do_gettimeofday+0x3a/0x100 │
Ap│Apr 2 14:39:06 kernel: [<c01056ce>] work_notifysig+0x13/0x19 │
Ap│Apr 2 14:39:06 kernel: =======================
.
.
.

for each application running.
i've ran memtest for checking if ram is bad, but there are no errors...
has anyone an idea what's going on?

vlad

ps: i've tried now a simple:

root@nukular:/etc # echo disk > /sys/power/state 
bash: echo: write error: Device or resource busy

starnge. it tries to suspend but after seconds it gets back to X, same as above.
wtf???
please help..

pps: sorry, more information: i'm using kernel26 with uswsusp from AUR and/or pm-utils on arch32.

Last edited by DonVla (2008-04-02 13:40:55)

DonVla · 2008-04-02 13:40:28

solved!

it seems now that the lirc_sir module has to be unload manually. till the last upgrade it was sufficient to stop the lircd before suspending. however it works now!

/me happy!

vlad

Arch Linux

#1 2008-04-02 12:49:29

[solved] precious suspend doesn't work anymore!!!

#2 2008-04-02 13:40:28

Re: [solved] precious suspend doesn't work anymore!!!

Board footer