Re: hibernation issue with kernel 2.6.23-gentoo-r3 at T41

[Daniel Drake <dsd@gentoo.org>]

Toralf Förster wrote:
> Today I tried to hibernate my ThinkPad but got the following :

And the outcome was what exactly? It didn't suspend, and hard-hung? Or 
didn't suspend, came back to a usable system? ...

> Dec  3 14:14:29 n22 c420 00000000 
> Dec  3 14:14:29 n22 dca29fb8 dca29f90 d30ad4c4 0851bf48 0851bf48 0851bfcb dca29fb8 c01036f1 
> Dec  3 14:14:29 n22 Call Trace:
> Dec  3 14:14:29 n22 [<c0135fe5>] refrigerator+0x55/0x80
> Dec  3 14:14:29 n22 [<c0121b2a>] get_signal_to_deliver+0x3ca/0x3f0
> Dec  3 14:14:29 n22 [<c01036f1>] do_notify_resume+0x91/0x6e0
> Dec  3 14:14:29 n22 [<c0113c61>] update_curr+0x141/0x150
> Dec  3 14:14:29 n22 [<c01c109d>] rb_erase+0x15d/0x280
> Dec  3 14:14:29 n22 [<c01136f7>] update_stats_wait_end+0xa7/0xe0
> Dec  3 14:14:29 n22 [<c028031b>] schedule+0x13b/0x2e0
> Dec  3 14:14:29 n22 [<c01040c2>] work_notifysig+0x13/0x19
> Dec  3 14:14:29 n22 =======================

Looks like your logger did not capture all the messages. Some important 
messages at the top were likely lost as a result. dmesg will have them, 
but you may have to increase the dmesg log buffer size in order to 
capture them all.

Did you press alt+sysrq+T or did all this come about as a result of the 
suspend?

Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/