How to debug resume (suspend) problems?
Geoffrey Leach
geoff at hughes.net
Sat Aug 28 21:17:17 UTC 2010
On 08/28/2010 01:21:37 AM, Felix Schwarz wrote:
> Am 27.08.2010 22:09, schrieb Konstantin Svist:
> > Check if numlock+capslock are flashing -- if they are, kernel
> crashed
> >
> > Check if you can switch to a virtual terminal with Ctrl+Alt+F2..F6
>
> No, I tried that before (sorry, did not mention that)
>
> > edit /etc/sysctl.conf and set sysreq = 1. After that, when you get
> a
> > freeze, try using REISUB (http://en.wikipedia.org/wiki/Reisub) to
> reboot
>
> I enabled the magic sysrq and verified that I can use it when the
> system
> is up and running. When provoked a resume failure, the system did not
> react to any of the sysrq combinations.
>
> So it looks to me like the system is just completely dead. Any ideas
> how
> I can gather more information? Suspend/resume worked well in Fedora
> 12
>
> and in the beginnings of Fedora 13 so I really want to have that
> feature
> back!
This is a good place to start.
http://www.mjmwired.net/kernel/Documentation/power/basic-pm-
debugging.txt
It also helps to know that /usr/sbin/pm-suspend (and related commands)
are shell scripts, so they can be executed with 'sh -x' to follow
what's happening. Finally, that happens on each suspend (aka suspend
to mem) and hibernate (aka suspend to disk) gets recorded in /var/log/
pm-suspend.log.
Good luck.
More information about the users
mailing list