Bugzilla – Bug 113709
Sound not restored after APM event on IBM T21
Last modified: 2007-02-16 14:04:27 UTC
As summary. This affects 9.3 (not had time to test 10.0 just yet). You can restart the sound system using 'rcalsasound restart', but this kills all apps using sound. It would be better to have the sound recovered without this problem. Trying to use the in-built recovery mechanisms in the powermanagement related config files doesn't help.
Which driver is used on this machine? Show /proc/asound/cards. If it's CS46xx, the PM won't work always, especially on laptops -> WONTFIX If it's an Intel chip, it should be fixed...
Also, try beta3. The PM stuff has been fixed in each release.
Beta 3 fails to respond to APM beyond locking the machine up. It is a CS46xx chip, but Windows naturally manages to revive this hardware without issue so there must be something that can be done. Note that rcalsasound restart does fix the problem, but the nasty effect is to kill all applications that have some interaction with the sound system. If the same effect could be achieved without killing apps off, things would be much better. *shrug*
If you unload snd-cs46xx before suspend, does lock up still occur? Do you have any kernel error messages from cs46xx driver when resume? The problem is that the behavior of controller doesn't follow to the datasheet at resume time. (Also we have not this hardware for debugging until now.)
The APM lock-up appears related to the framebuffer drivers being loaded. The rcalsasound restart approach fixes sound on resume, but I haven't had the time yet to look into the logs for kernel error messages. I only get a couple of evenings a week to look at non-work related stuff.
For testing just only the sound stuff, you can use "alsactl". Run like: # alsactl power 0 D3hot to suspend the sound function, and # alsactl power 0 D0 to resume. Check the behavior of sound devices with the sequence above. Also, please show the output of "lspci -nv", and attach any relevant kernel messages before/after suspend/resume.
No reaction on this bug for more than 17 months. Closing as CANTFIX.