On Mon, 31 Jul 2006, Stefan Seyfried wrote:

I just installed powersaved on my Debian testing system. My kernel supports
suspend to disk via swsusp, and it used to work (and still works) fine if I
suspend the system using the "hibernate" command. If
I try to suspend it with powersave, however, the system will suspend as
usual. During the reboot, however, it will at some point display

Restarting tasks...

This is a message from the kernel during resume which is printed after
resuming the drivers and before starting the userspace again.

Yes, I found the corresponding source file. BTW: it's a hand-compiled kernel, so if it helps to add some extra line in the corresponding function to print which tasks are restarted, I can do that. However, I would be happy if someone could tell me _what_ to change in the source.

and at that point, it hangs. Not even the "magic SysRq keys" work any more.

[but it works with "echo disk > /sys/power/state"]

unloaded. Can you retry with UNLOAD_MODULES_BEFORE_SUSPEND2DISK="NONE"?
(Yes, this configuration file syntax with default values if the string is

I already tried this, but it does not help.


suspend2disk initiated: 2006-07-23 02:15:51
Debug info follows here, please include in your bug reports. Thanks.
--------------------------------------------------------------------
Loaded modules:
Module Size Used by
cpufreq_ondemand 5276 1
cpufreq_userspace 3672 0

Ah. Another thing worth trying (if the ohci1394 is not the problem) would
be to do a "powersave -l" before suspend. There were problems with ondemand
during suspend/resume and we worked it around at some point by just switching
to a fixed cpu frequency during suspend. Not sure if your powersave version
already does that, but doing "powersave -l" before suspend will ensure that
it is on the lowest cpu frequency. However, i doubt this is the problem since
that would also hit you when manually suspending. We never know, though :-)

Does not help either, sorry.


So if a patching power/process.c to print some extra information might help, I could do that. In any case, the " done\n" ending the function is not printed any more, so the problem must occur somewhere there.


Thanks,
Norbert

_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel

Reply via email to