[hardy] After suspend sound isnt working anymore

[Christian Becker]

In Gutsy suspend worked fine on my IBM Thinkpad T23.
In Hardy Sound isnt working anymore after suspend.

WORKAROUND: sudo rmmod snd_intel8x0 && sudo modprobe snd_intel8x0
WORKAROUND: gksu /etc/init.d/alsa restart

[Christophe Sauthier (christophe.sauthier)]

I encounter the same problem here of no sound after suspend/resume on the latest hardy kernel (2.6.24-11).

[Christian Becker (c-becker-88)]

Also same problem with 2.6.24-12-generic newest updates installed...

[Christian Becker (c-becker-88)]

chris@schleppmich:~$ sudo rmmod snd_intel8x0
chris@schleppmich:~$ sudo modprobe snd_intel8x0

This solves the problem after a suspend...

[Heiko (heiko-barg)]

Same here with Realtek / Intel HD-Audio Codec:
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)

(Hardy with all updates, x64)

[gmicsko (gmicsko)]

Same here with Intel ICH6 Hi-Def Audio:

00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)

Kernel: 2.6.24-12-generic

[P (p92)]

Well with thinkpad X40 I have NO MORE SOUND in hardy even after a power off / power on !

kernel 2.6.24-12-generic

00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
        Subsystem: IBM Unknown device 0558
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 17
        Region 0: I/O ports at 1c00 [size=256]
        Region 1: I/O ports at 18c0 [size=64]
        Region 2: Memory at d0100c00 (32-bit, non-prefetchable) [size=512]
        Region 3: Memory at d0100800 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

[gmicsko (gmicsko)]

Well, with today's updates (pulseaudio, GNOME, etc.), seems like problem solved for me. After resume from suspend sound works again.

[Christian Becker (c-becker-88)]

Hmmm, dont know if its fixed, because pulseaudio makes some problems on my thinkpad, but will tell you the next days if its fixed for me...

[Christian Becker (c-becker-88)]

After a suspend i must kill pulseaudio, because its blocking my audio device... Sound looks like its playing, but I cant hear anything..

then I reload my soundmodule:

rmmod snd_intel8x0
modprobe snd_intel8x0

and then I restart pulseaudio.

Voila, sound is working again.

I put all that stuff into a script, but sucks, its just a workaround, so sound in hardy after suspend is still broken for me.

regards
chris

[TerpInHotLanta (ccampjr)]

Ditto for me except my module is snd_hda_intel

kill pulseaudio
remove module
load module
start pulseaudio

Fingers crossed,
Charlie

[Christian Becker (c-becker-88)]

still unfixed in final. This should be HIGH PRIORITY!!

[Rolf Leggewie (r0lf)]

Christian, where is your patch?

[anystupidname (anystupidassname)]

Stinkpad T30 here with same issue. All updates applied on hardy and suspend knocks out sound.
rmmod snd-intel8x0 and rmmod -f snd-intel8x0 both fail to unload module though with
ERROR: Module snd_intel8x0 is in use
and
ERROR: Removing 'snd_intel8x0': Resource temporarily unavailable

So restart required... Pretty lame not being able to use suspend.

[Jameson Williams (jamesonwilliams)]

I can confirm this is still present for:

Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
2.6.24-16-generic

This release has a lot of bugs with suspend - huh? See also 3945abg (and other networking) issues.

[Spuerhund (spuerhund)]

I can confirm this for an Intel ICH9 HD Audio Controller and Ubuntu 8.04 x86_64 including all available updates. After restarting sound is working again perfectly.

[Christian Apolloni (christian-apolloni)]

I can confirm this too with a fully updated hardy 64bit:

00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
 Subsystem: ASUSTeK Computer Inc. Unknown device 829f

Please assign at least medium importance since in many cases this bug makes suspend useless.

[Burke (bschrammel)]

Confirmed on this Thinkpad T23, too.

A manual

sudo /etc/init.d/alsa-utils restart

solves it for me till next suspend.

[Prateek Karandikar (prateek.karandikar)]

Confirmed on Acer Aspire 4720 with Kubuntu Hardy.

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)

aplay, mplayer, Amarok, etc don't complain, but no sound is heard.

Tried sudo /etc/init.d/alsa-utils restart, rmmoding and modprobing snd-hda-intel, in different combinations, but no luck. I wish there was an easy foolproof way to start the sound system from scratch, exactly as if it had been started after a bootup (without restarting the computer).

[Prateek Karandikar (prateek.karandikar)]

Forgot to add, sound did work after resuming from suspend on the same laptop with Kubuntu Gutsy. Though Gutsy needed manual installation of a newer version of ALSA from source to get sound working in the first place.

[Christian Becker (c-becker-88)]

Thank you Burke for your workaround.

I just dropped a Icon on my desktop with "gksu /etc/init.d/alsa restart" and this is a workaround which isn't as bad.

But would be nice if this got's fixed with the next update cycle...

regards
chris

[Christian Apolloni (christian-apolloni)]

I used another workaround. I put the following line in /etc/modprobe.d/alsa-base.
This way after the resume I get the sound back without having to restart alsa.

options snd-hda-intel model=6stack-dig

Probably you have to adapt it to your sound card model with the alsa documentation and some trial-and-error (that's what I did).

[Prateek Karandikar (prateek.karandikar)]

Restarting alsa-utils or reloading snd-hda-intel did not work for me. sudo /sbin/alsa force-reload after resuming from suspend got the sound back.

This is on Kubuntu 8.04 on an Acer Aspire 4720. Relevant lines from lspci -v:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
        Subsystem: Acer Incorporated [ALI] Unknown device 011d
        Flags: bus master, fast devsel, latency 0, IRQ 22
        Memory at f0500000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [70] Express Unknown type IRQ 0

[Martin Emrich (emme)]

Same here:

snd-hda-intel
Mainboard:
  Gigabyte GA-MA69GM-S2H Mainboard (AMD RD690 + SB600)
Audio chip:
  [ 712.103980] hda_codec: Unknown model for ALC882, trying auto-probe from BIOS...
  [ 712.115695] ACPI: PCI Interrupt 0000:01:05.2[B] -> GSI 19 (level, low) -> IRQ 22

The problem is that one cannot just reload the module, as many apps are using it, in my case it's always the GNOME mixer-applet, and in most of the cases a player (rhythmbox, ...).
I'm playing around with some module options now.

[Nikos Efthimiou (nikos-efthimiou)]

 Exactly the same to me.

82801H (ICH8 Family) HD Audio Controller
Intel Corporation (Toshiba America Info Systems)

[ry (ry-tinyclouds)]

Like PascalCavy, my sound is also not returning now after reboot. (Thinkpad T30)
I had run this script
--- CUT ---
  #!/bin/sh
  # discover video card's ID
  ID=`lspci | grep VGA | awk '{ print $1 }' | sed -e 's@0000:@@' -e 's@:@/@'`

  # securely create a temporary file
  TMP_FILE=`mktemp /var/tmp/video_state.XXXXXX`
  trap 'rm -f $TMP_FILE' 0 1 15

  # switch to virtual terminal 1 to avoid graphics
  # corruption in X
  chvt 1

  # write all unwritten data (just in case)
  sync

  # dump current data from the video card to the
  # temporary file
  cat /proc/bus/pci/$ID > $TMP_FILE

  # suspend
  echo -n mem > /sys/power/state

  # restore video card data from the temporary file
  # on resume
  cat $TMP_FILE > /proc/bus/pci/$ID

  # switch back to virtual terminal 7 (running X)
  chvt 7

  # remove temporary file
  rm -f $TMP_FILE
--- END CUT ---

Pascal, did you find a solution?

[P (p92)]

hi!
my problem was solved by the latest kernel, just a while after hardy was released. I have no more sound problems without doing anything special. Check the mixer levels maybe...

[Bob Myers (portlandbob)]

Thanks Prateek this worked for me also: sudo /sbin/alsa force-reload after resuming from suspend

Mainboard:
  ABIT AN52 AM2 NVIDIA nForce 520 MCP ATX AMD
Audio chip:
  nVidia Corporation MCP65 High Definition Audio

relevant lines from lspci -v

00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio (rev a1)
 Subsystem: ABIT Computer Corp. Unknown device 1c36
 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 19
 Memory at fe024000 (32-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>

There has to be a better way.

[Axel Pospischil (apos)]

Hi there,
I am on an Thinkpad R31 and no sound after hibernation / resume. See attached lspci -vv. Im running the latest updates of today and kernel generic 2.6.24-18 and module snd-intel8x0.

The solution with restarting alsa-utils or "alsa force-reload" works, but only __after__ I logged into the session. Restarting alsa-utils however does not force to shutdown associated programs like the sound-applet ;)

Putting this into the "/etc/acpi/resume.sh" (or other relevant files during resume) has NO effect (!!! very strange !!!).

When the machine suspends, I hear a knocking sound when the sound shuts down. Same on resume. I hear the same knocking sound when I manually do a "force-reload" of alsa. But only a reload of alsa after logging in has success getting sound working.

I searched and found according bug #151111 (HP Laptops), bug #11149 and bug #223742 (Serval Performance - fixed with module options snd-hda-intel model=toshiba).
But description for the fix of the bugs is neither not applicable for thinkpads nor valid (links are dead for released fixes).

After hours of searching about hardy and hibernation I found out, that ubuntu hardy uses pm-utils for this purpose which relevant directories are "/usr/lib/pm-utils/sleep.d" and "/etc/pm-utils/sleep.d".

So I put a file called "80alsa" into "/etc/pm-utils/sleep.d" (see attachment) reloading alsa-utils and now (at almost 2 o'clock) my sound worked after resume ;)

This leads me into some general questions:
1. Why do the acpi helper script do not work like expected? Are they used anyhow?
2. Has "/etc/default/acpi-support" any effect?
3. Would not be a global solution reloading alsa-utils better, than fixing each driver with an alsa-base module option?

Hope this helped. Good night.

[wastedfluid (wastedfluid)]

Axel,

Where do you put this file that you posted for a fix?

[Samsam (abacusje)]

Tried it all and only the ' sudo /sbin/alsa force-reload ' solution Prateek gave worked for me. Finally I got my sound back.
I use Ubuntu hardy 8.04 on a FL92 compal based BTO laptop (15W26+) with the snd-hda-intel IHC8 type (with realtek ALC268 I think) of sound module.
 I'm happy to have found a workable solution for the suspend function since I like to use that a lot on my laptop. It is not functioning really perfect yet, but at least i can use it now. Hibernate still remains a problem, but that seems to be another story. Thanks everyone.

[cyoo (cyoo96)]

I confirm the same problem. Like Samsam, ' alsa force-reload ' will enable sound after waking up from hibernation. This is not a good solution because it will kill all programs that are using sound. I believe there needs to be a proper update for the pm-utilities in conjunction with the kernel. As it currently stands, we should say that hardy does NOT provide hibernate/suspend.

BTW, I still cannot make hardy recognize my microphone.

Toshiba Satellite A205-S5825 with 2G RAM
kernel: 2.6.24-19-generic

[ka_bra (ka-bra)]

Same bug here on a T23 with sound after suspend/standby.

Problem is discussed on ubuntuforums.org with some helpful solutions (Post 9 & 10) in the following link:

http://ubuntuforums.org/showthread.php?p=4844306

I just tried the hint in post #9 and it brings sound back right after standy/suspend. But maybe post #10 is the better alternative.

[Axel Pospischil (apos)]

@wastedfluid

Sorry, I should have named the info text "80alsa_restart".
As I described I put it into "/etc/pm-utils/sleep.d".

It has to be executable, so do: "chmod 755 /etc/pm-utils/sleep.d/80alsa_restart"
The script does exactly what solutions mentioned in the last post (ubuntuforums.org #9) suppose to do).

You can edit this file and put e.g. "alsa force-reload" into it if this solves you problem. But be aware, the "alsa force-reload" really kills __all__ applications that are using the sounddriver !!!

On the other side you better should use the official script syntax of the "pm-utils" scripts, what is decribed in [ubuntuforums.org #10] is a very very bare "pm-utils" script, has no error handling at all and does not differ between suspend and resume. So look into the default scripts located in "/usr/lib/pm-utils/sleep.d" - it is really easy to write one.

REMEMBER:
1. Scripts in "/etc/pm-utils/sleep.d" will not be overridden on system updates.
2. Scripts in "/etc/pm-utils/sleep.d" have higher priority, so a script in there with the same name as in "/usr/lib/pm-utils/sleep.d/" will be executed, the default one NOT.

[Mark Stosberg (markstos)]

On a ThinkPad T23, simply unmuting the right volume levels fixes this. Instructions for making this happen automatically are here:

http://www.thinkwiki.org/wiki/Installing_Ubuntu_on_a_ThinkPad_T23#Sound_After_Suspend

[atorch (atorch)]

I'm in the same situation as Prateek Karandikar, who wrote:

"restarting alsa-utils or reloading snd-hda-intel did not work for me. sudo /sbin/alsa force-reload after resuming from suspend got the sound back."

Here's my lspci:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
 Subsystem: COMPAL Electronics Inc Unknown device 0025
 Flags: bus master, fast devsel, latency 0, IRQ 23
 Memory at f8400000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: [50] Power Management version 2
 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
 Capabilities: [70] Express Unknown type IRQ 0

I'm running ubuntu 8.04, 2.6.24-19-generic kernel, gnome 2.22.2

[Michael Leow (jweng-leow)]

Just wanted to add another case observed. Only solution was sudo /sbin/alsa force-reload; tried the other suggestions but those did not work!

Details below:
Dell Vostro 1510, Ubuntu 8.04.1, 2.6.24-19-generic kernel

lspci:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
        Subsystem: Dell Unknown device 0273
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at f8500000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>

[Kim Alvefur (zash)]

Zepto ZNOTE 3215W which is Compal based (motherboard IFL91)
Intel 82801H (ICH8 Family) HD Audio Controller

reloading pulseaudio and module snd-hda-intel brings back audio

[Rolf Leggewie (r0lf)]

I am afraid we might have a couple of bugs with similar effects mixed up in here. Let's try and untangle it. Is this more likely to be a kernel or an alsa problem? alsa is certainly affected, but is it really the most likely candidate for where this bug is located?

[Martin Emrich (emme)]

That's right. For many people here, somehow reloading/restarting ALSA helps, but not for me. I have to reload the entire snd-hda-intel module, which is only possible if I remove the mixer applet (and close any other audio application) every time. So my candidate is the linux package.

[GBTexas (d2audio)]

Acer Aspire One with Intel Atom.

Netbook Remix: Audio does not work after resume from suspend. The work-arounds in this post are not successful.

[Daniel T Chen (crimsun)]

This is not an alsa-utils issue but a kernel issue (specifically alsa-kernel/driver). People are mistakenly thinking that restarting the alsa-utils initscript fixes things, but note that doing so only stores and restores, in that order, the volume levels. The reason that forcibly reloading the kernel driver via /sbin/alsa works is that doing so forces a complete reinit of the codec.

What will assist the bug triagers? Please run the alsa-info.sh script referenced in my profile, and attach the output (either codec dump or generated URL from script) to this bug.

[Kim Alvefur (zash)]

http://www.alsa-project.org/db/?f=a163d0d347b281315dd36872ae677526f8ce11fb

[Martin Emrich (emme)]

http://www.alsa-project.org/db/?f=f8e66bc3beae6d1b7f0b1b245586e12a918799ea

(I'm in the group where initscript-restarting alone does /not/ help)

Ciao

Martin

[Michael Leow (jweng-leow)]

On a Dell Vostro 1510; alsa-info output below:

http://www.alsa-project.org/db/?f=b8cdfa72509191422fcdb6fcb12f7efa5b49f984

Had to issue "alsa force-reload" to get sound working again after suspend.

[atorch (atorch)]

http://www.alsa-project.org/db/?f=038cf2368da438b63891bbf12a3c3a147d04db26

I'm one of the "restarting alsa-utils or reloading snd-hda-intel did not work for me. sudo /sbin/alsa force-reload after resuming from suspend got the sound back" people.

[baroy4 (blackfeild)]

On IBM Thinkpad t30

"sudo /sbin/alsa force-reload after resuming" worked just fine!!

problem solved
thanks guys.

[RPDiep (renediepstraten)]

http://www.alsa-project.org/db/?f=d34770cdab77e625a4c42e18abf7ef7c36e96d0d

[Carl Meyer (carljm)]

I had this problem on a Dell Vostro desktop:

00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)

Christian Apolloni's solution fixed it for me, I put "options snd-hda-intel model=6stack-dig" in /etc/modprobe.d/alsa-base

alsa-info.sh results here: http://www.alsa-project.org/db/?f=1ffa55cf34dab5741dcf11f59c312d0965590387

[Martin Emrich (emme)]

Without changing anything, I today noticed that my sound continued to work after suspend-to-RAM (intrepid amd64). I'll use suspend more often in the next days and see if it works reliable now.

[Henry Gomersall (hgomersall)]

On a Dell Inspiron 9400 with snd-hda-intel, I get the same problem.

There is an interesting effect where from a fresh boot, the suspend/resume works fine. Sound works and everything is great. The problems seem to be after I have run Banshee using Gstreamer.

Note that I can happily run mplayer or flash videos with sound time and again and then suspend and resume apparently fine.

Running sudo /sbin/alsa force-reload will enable Banshee to play audio again. At this point, Mplayer no longer works, with the warning:
AO: [pulse] Failed to connect to server: Connection refused
Could not open/initialize audio device -> no sound.

[mikey (abc-mikey)]

I have the same issue on Ubuntu Intrepid (8.10) with kernel 2.6.27-9:

My soundcard is an Audigy SE and I need to do the following to make it work where snd_ca0106 is the module for my sound card.

Make a script for suspend and resume:

sudo gedit /etc/pm/sleep.d/99sound

Paste in the script to stop and restore the sound module (down to the line with exit)

#!/bin/bash

case "$1" in
    resume|thaw)
        modprobe snd_ca0106
     ;;
     suspend|hibernate)
        modprobe -r snd_ca0106
    ;;
esac
exit $?

Make it executable

sudo chmod +x /etc/pm/sleep.d/99sound

[Nais (ftpetracca)]

I'm using Intrepid (amd64) upgraded from a Hardy installation and sound isn't resuming upon restoring from suspend. Sound is provided by an on-board Sound Blaster live 24-bit, using the ca0106 module.

I only got suspend working recently after playing in my BIOS, so I can't say how this worked before Intrepid.

[thgreasi (thgreasi)]

The problem insists with kernel 2.6.27-11
I have a Audigy LS using snd_ca0106 and no (manual or not) solution worked for me so far

[Mark Stosberg (markstos)]

I confirmed tonight that sound-after-suspend fails when using Intrepid ( 2.6.27-7 ) on a ThinkPad T22.

I also confirmed Axel's workaround published above:

https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/198218/comments/35

I did have to modify the posted file to uncomment the "force-reload" line, which as other mentions will kill all applications that are using sound. Still, I find that better than not having sound work at all after a suspend/resume cycle.

[somejan (somejan)]

confirming this is also affecting me.

laptop: HP Pavillion dv7 with intel IHC9 family chipset
driver: snd_hda_intel
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

After suspend or hibernate sound becomes unusable (it only stutters). After reloading the snd_hda_intel kernel module it works again, and strangely enough that fixes it until the next reboot, i.e. I can then suspend/hibernate as often as I want.
'sudo alsa force-reload' also works as it also reloads the kernel modules.

[Patricio (patricio-stwing)]

The sound also stops working after hibernate in the HPdv6885se with Jaunty.
The workaround "sudo /etc/init.d/alsa-utils restart" works in this case and, so far, it is minimally invasive as it does not kill the sound applications.

[penalvch (penalvch)]

Christian Becker, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, please run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Phillip Susi (psusi)]

Expired.