Sound broken after resume of Suspend - Toshiba P100

[rax_m]

Hi,

Ubuntu Feisty Fawn
Toshiba P100-429
Bios updated to 3.30
DSDT manually fixed and applied to get sound working

After suspending to ram and resuming (which seems to work wonderfully works), the sound no longer works. In fact there are no sound cards even detected. However, if I reboot then everything works as expected.
I know this might be related to other bugs, but I thought this might be separate based on the manual stuff I've done.

Cheers
Rax

[trollord (trollenlord)]

May or may not be related:
http://bugzilla.kernel.org/show_bug.cgi?id=7228

[rax_m (rax-m)]

So.... what should i do now?

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Leann Ogasawara (leannogasawara)]

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

[rax_m (rax-m)]

This is still an issue on Intrepid.. I forgot about this bug and actually opened a new one. I'm not sure which should remain open.
https://bugs.launchpad.net/bugs/314060

[Leann Ogasawara (leannogasawara)]

Hi rax_m,

Would you be wiling to test the latest pre-release of Jaunty (currently Alpha 3) - http://cdimage.ubuntu.com/releases/jaunty/ . You should be able to test via a LiveCD. Please let us know your results. Thanks.

[rax_m (rax-m)]

Hi Leann,

Unfortunately due to bandwidth limitations I cannot download the alpha.

Also, ever since I reported the bug, I've been told to keep trying the next release. I don't think this is the right solution. Because when I try the Januty release, it will most likely not work and then I will be told try the next release. With all due respect for the hard work that is put into each release by the devs, is there no other way to fix this?

Thanks
Rax

[Andy Whitcroft (apw)]

@rax_m -- that is a common approach to problem solving. Find a place where the thing works and compare that place to where it does not work. The delta there gives you hints as to the cause.

Looking at the patch suggested in the first comment, that seems to be about sound not working at all and was fixed in 2.6.24, so that is unlikely to be relevant.

Since then it looks like you have switched to Intrepid, but the bug is still there. Could you confirm that you are now running Intrepid, and also attach the output of the alsa-info script from the URL below on your system before suspend:

    wget http://alsa-project.org/alsa-info.sh

Also could you then suspend and resume the machine and re-rerun the script and attach the results from there also. Finally could you attach the dmesg output after you have resumed.

[rax_m (rax-m)]

Hi Andy.

thanks for the info. Here is the info you requested.
Before suspend
http://www.alsa-project.org/db/?f=7a92a06b4c9f49d136b7027de2c740ce3801b943

After resume
http://www.alsa-project.org/db/?f=9d1c32cd6e9ab67a37d551a6664a9cb7bcd05ebc

Also attached is the dmesg output you requested.

[rax_m (rax-m)]

Also, to confirm, I am now running on Intrepid.
I am also using the Nvidia restricted driver as well as full desktop effects.

[Stefan Bader (smb)]

This bug unfortunately did not receive much care lately. Sorry. What is the current situation? Which release are you currently on and, in case you moved on to Jaunty, did this improve the problem?
From the two alsa logs posted, it looks like the card (from the view of alsa) is detected after the resume. You might want to try to use alsamixer aplay to check that.
One other idea would be to try to remove snd-hda-intel on suspend. See the documentation for pm-suspend on how to add module names for that (should be SUSPEND_MODULES="snd-hda-intel" in a file in /etc/pm/config.d).

[rax_m (rax-m)]

Thanks for the response Stefan. I'll give this a try soon.
I'm still on Intrepid.. will move to Jaunty as soon as I upgrade my laptop hdd (this month!).

[rax_m (rax-m)]

My /etc/pm/config.d/00sleep_module file now looks like this (hope I got it right):

# The sleep/wake system to use. Valid values are:
# kernel The built-in kernel suspend/resume support.
# Use this if nothing else is supported on your system.
# uswsusp If your system has support for the userspace
# suspend programs (s2ram/s2disk/s2both), then use this.
# tuxonice If your system has support for tuxonice, use this.
#
# The system defaults to "kernel" if this is commented out.
# SLEEP_MODULE="kernel"
SUSPEND_MODULE="snd-hda-intel"

Unfortunately, this still does not work for suspend. (I noticed for the first time today that hibernate is actually working just fine and sound works after resume, but hibernate takes almost as long as a reboot).

If I use alsamixer or aplay after a suspend, I don't get any errors :

rmistry@rmistry-laptop:~/Examples$ aplay fables_01_01_aesop.spx
Playing raw data 'fables_01_01_aesop.spx' : Unsigned 8 bit, Rate 8000 Hz, Mono

[rax_m (rax-m)]

I've also attached my pm-suspend.log file if it's useful.

[rax_m (rax-m)]

This issue still occurs with Jaunty.

[yuval aviel (yuval-aviel)]

happens also here (Jauny, kubuntu 9.04), hda_indel internal sound card on Dell Precision M6300.

alsa info is here:
http://www.alsa-project.org/db/?f=52b39489e2f8697b189dffcd60e9b86065f3cf87

[Stefan Bader (smb)]

@rax_m, sorry for the long delay. Unfortunately I got sidetracked quite a bit. It seems the variable name is not completely correct, it should be SUSPEND_MODULES (comma separated list of modules). One other thing that seems to happen sometimes is that some channels get muted after suspend. Maybe you could check that too.

@yuval aviel, thanks for your report. Unfortunately, despite of using the same module, hardware is usually so different between different laptops. So it would be better to open a new bug for your Dell. Thanks.

[yuval aviel (yuval-aviel)]

Solution that works for me:

> alsa force-unload
> alsa force-reload

FYI

[madbiologist (me-again)]

Is this still occurring in Ubuntu 10.04 "Lucid Lynx"?

This issue might be fixed upstream in kernel 2.6.35-rc5.

From the changelog:

commit ac0547dc62e67a3e0b0c1628b6e49efba8f517db
Author: Takashi Iwai
Date: Mon Jul 5 16:50:13 2010 +0200

    ALSA: hda - Restore cleared pin controls on resume

    Many codecs now clear the pin controls at suspend via snd_hda_shutup_pins()
    for reducing the click noise at power-off. But this leaves some pins
    uninitialized, and they'll be never recovered after resume.

    This patch adds the proper recovery of cleared pin controls on resume.
    Also it adds a check of bus->shutdown so that pins won't be cleared at
    module unloading.

    Reference: Kernel bug 16339
     http://bugzilla.kernel.org/show_bug.cgi?id=16339

    Cc: <email address hidden>
    Signed-off-by: Takashi Iwai

A PPA of this kernel is available at http://kernel.ubuntu.com/~kernel-ppa/mainline/

[yuval aviel (yuval-aviel)]

not a problem any more.
See my comment before for system details. I've upgraded to 10.04 since then.

[rax_m (rax-m)]

Hi

Thanks for the feedback.
Unfortunately my laptop was stolen so I don't experience the problem anymore ;)

[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.