Bugzilla – Bug 114787
snd_cs46xx breaks suspend (Thinkpad T20)
Last modified: 2007-08-11 15:28:01 UTC
- Standby: Notebook goes into standby but does not wake up again (screen is already there). Tried from X. - Suspend to RAM (1): Stopping tasks seems to be finished, nothing happens afterwards -- does not suspend. Tried from X and from console with network down and e100 module unloaded - Suspend to RAM (2):behaves like Standby. Tried from console (X running, no modules unloaded) - Suspend to disk: behaves like Suspend to RAM (1). powersave: powersave-0.10.9-2 dbus: dbus-1-0.35.2-4 hal: hal-0.5.4-2 kernel: 2.6.13-3-default
Created attachment 48501 [details] hwinfo
Created attachment 48502 [details] suspend2disk.log
Created attachment 48503 [details] suspend2ram.log
Created attachment 48504 [details] standby.log
Suspend-to-disk fails for me in the same way. My machine is a 1000MHz Pentium III desktop.
try debugging it as described in http://www.susewiki.org/index.php?title=ACPI_suspend, this is not a powersave bug, so the powersave logs are worthless. We'd actually need messages during suspend (T20 has serial port so this should be easy) if it still fails after that.
Suspend to disk works if sound module snd_cs46xx gets unloaded and the SUSPEND2DISK_SHUTDOWN_MODE is set to 'shutdown'. This can be a problem if applications are activly using the sound device. Is there a way to find out which applications are using the device in order to kill them? I did an init script which just kills kmix and added that to the 'sleep' config file ... but this solution is not really clean.
so this is a sound driver bug actually.
It's know that PM with cs46xx on TP doesn't work for a long time... A better h/w information from IBM would be required to fix this.
Suspend2Disk works well without unloading if you enable the "thinkpad=1" module option. This doesn´t solve the issue that there is no sound output after resume without reloading the sound driver; at least /etc/init.d/alsasound restart should be executed. Sebastian
We will not fix this bug for 10.0 anymore. If the bug still exists in openSUSE 10.3, please reopen and change the product.