Hi,
On Mon, Jul 31, 2006 at 01:30:57AM +0200, Norbert Schuch wrote:
> [Note: This has already been posted on sourceforge, where I was suggested
> to discuss the problem here.]
> Hi,
>
> 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.
> and at that point, it hangs. Not even the "magic SysRq keys" work any more.
This smells like some driver bug. Probably a driver that has a kernel-thread
is not behaving nicely and locks the machine up once the thread gets
restarted (just a wild guess).
> I already tried to copy the modules blacklist from hibernate, but it did
> not help.
>
> Unfortunately, the system hangs before it can write to any log files. FYI,
> I attached the
> /var/log/suspend2disk.log
good.
> Update relative to the sf.net-Post:
> The system can even be suspended by simply
>
> # echo disk > /sys/power/state
>
> without unloading any modules. I also changed the powersave-config-file not
> to unload any modules, but the system still hangs at the same point. What
> exactly happens when this message is printed? Is it printed by the kernel
> ('cause I didn't see it when I suspended "by hand") or by powersave?
The attached suspend2disk.log shows that at least ohci1394 was still
unloaded. Can you retry with UNLOAD_MODULES_BEFORE_SUSPEND2DISK="NONE"?
(Yes, this configuration file syntax with default values if the string is
empty probably was not a too good idea of mine, i noticed this already...)
> Thanks a lot in advance,
>
> Norbert
>
> P.S.: I was suggested to see which modules are unloaded by hibernate. As
> far as I can see, there are no modules in the hibernate blacklist which run
> on the system, and hibernate does not log that it unloads any modules,
> although there is a log file line for calling the unload routine.
Ok, and as you can suspend manually by echoing into sys/power/state, it
really looks like the unloading of ohci1394 might be the problem since i
do not see that powersave would do anything else differently (at least
nothing that should matter here).
> $ cat /var/log/suspend2disk.log
>
> 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 :-)
> powernow_k7 7144 0
..
> ------------------------------------------------------------------------------
> Unloading modules: ('usb_storage sbp2 ohci_hcd uhci_hcd stir4200 ohci1394
> ipw2200 rt2500 prism54 ath_pci r8169 lt_modem Intel536 Intel537
> ndiswrapper' configured)
> checking usb_storage
> checking sbp2
> checking ohci_hcd
> checking uhci_hcd
> checking stir4200
> checking ohci1394
> # trying to unload: ohci1394
> unloaded: ohci1394
here it is unloading ohci1394.
--
Stefan Seyfried | "Please, just tell people
QA / R&D Team Mobile Devices | to use KDE."
SUSE LINUX Products GmbH, Nürnberg | -- Linus Torvalds
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel
