Suspend kills sound on IBM T21

[Phil Stopford]

Feisty Fawn freshly installed on a IBM T21 with 512 MB of RAM. Suspending from the GNOME dialog works without error, but resuming the machine shows that the sound hardware has not been restored correctly. I have not been able to get it back, even by the usual trick of restarting alsa (/etc/init.d/alsa-utils restart completes without error, but no sound available; adjusting volume does not help)

Rebooting is the only option.

[Dan O'Huiginn (daniel-ohuiginn)]

Thanks for taking the time to report this bug. Please include the information requested from [WWW] https://help.ubuntu.com/community/DebuggingSoundProblems as separate attachments.

[Phil Stopford (phil-stopford)]

amixer output

[Phil Stopford (phil-stopford)]

asoundconf list output

[Phil Stopford (phil-stopford)]

dmesg output

[Phil Stopford (phil-stopford)]

interrupts output

[Phil Stopford (phil-stopford)]

lspci output

[Phil Stopford (phil-stopford)]

sndstat output

[Phil Stopford (phil-stopford)]

/etc/asound.conf does not exist

[Dan O'Huiginn (daniel-ohuiginn)]

Thanks for that information, Phil.

[Mackenzie Morgan (maco.m)]

By the way, does this bug still exist in Hardy or Intrepid?

[Leann Ogasawara (leannogasawara)]

The 18 month support period for Feisty Fawn 6.10 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result, we are closing the linux-source-2.6.20 kernel task. However, the Intrepid Ibex 8.10 release is set to come out at the end of the month. It contains a newer 2.6.27 kernel. It would be good to confirm if this is still an issue with Intrepid - http://www.ubuntu.com/testing . If the issue still exists, please add the linux kernel task to this bug report. This can by done by going to:

https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/126653/+distrotask

Then change the Source Package Name to be "linux" instead of "linux-source-2.6.20" and click Continue. Thanks.

[Aliaksandr Dzeshchanka (lazy)]

Even 9.04 still has this bug.

[Mackenzie Morgan (maco.m)]

Can you download the bash script from http://alsa-project.org/alsa-info.sh and run it (with bash, not sh, which is dash) and post the link it gives you?

[Mackenzie Morgan (maco.m)]

By the way "sudo alsa force-reload" is likely the workaround command you wanted.

[axoin (axoin)]

Can confirm this with 9.04 BETA. Output as required: http://www.alsa-project.org/db/?f=7ed5731156f9b3e55271bf82e1a3889cd31ce2ff. Please tell me how to help further.

[Aliaksandr Dzeshchanka (lazy)]

Script's output after suspend/resume

[Daniel T Chen (crimsun)]

Workaround is to issue `sudo alsa force-reload'

[Aliaksandr Dzeshchanka (lazy)]

Maybe, there is a way to add it to some scripts running automatically after resume?

[axoin (axoin)]

Daniel, your workaround brings the sound back. However it does not solve the problem, as all apps having access to the sound as firefox or gnome-mixer-applet are killed, too. This is very annoying. Isn't this a duplicate of Bug #11149?

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.