speakers are unmuted after resume from suspend while headphones are plugged in

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please add the output requested at
https://help.ubuntu.com/community/DebuggingSoundProblems ? Thanks in
advance.

 status needsinfo
 assignee <email address hidden>

Standard info

aadebug output

Sometimes I have a reverse problem - when I have a headphone plug plugged in to the headphone jack right from the beginning of the system boot, the headphones work ok but when I unplug them the laptop speakers are mute.

Another problem: after returning from hibernation the laptop speakers were turned on even though the headphones were plugged in.

Also when I boot without headphones plugged, the laptop speakers stay turned on when I plug the headphones later (I can hear the sound in both the headphones and the speakers). This is very annoying.

I've installed a ck-patched kernel from http://ubuntu.iuculano.it/dists/feisty/ck-kernel/ and now sound is working fine after resuming from sleep. Hibernation doesn't work though.
I don't know which of the ck-patches is responsible for the fix.

Ok, cancel that - the error still appears sometimes.

I've finally found a solution - removing snd_hda_intel before sleep.
You have to put:
MODULES="snd_hda_intel"
in /etc/default/acpi-support
(near "# Add modules to this list to have them removed before suspend and reloaded" line)

This solution still doesn't solve it completely - the problem is back after few suspendtoram/resume cycles.

This problem still exists on gutsy.

I don't think this bug is a duplicate of bug #94566 - my problem appears only after resuming from suspend.

I've added new logs to show the current image of my situation.

Also I'm not unloading the snd-hda-intel module before sleep anymore - it didn't help.

Is this symptom still reproducible in 8.10 alpha?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

I have the same problem on a Thinkpad X41 tablet with Ubuntu 8.10.
Attached are the hopefully sufficient logs from https://help.ubuntu.com/community/SoundTroubleshooting

I have a similar problem on a Thinkpad X41 with 8.10 and also with 9.10. After suspending two times the headphone jack is not functional any more. All sound is played throw the laptop speaker.
Should I open a new bug for this?

I have exactly the same problem on my Thinkpad X41. I had it in 8.10 and still have it in Jaunty. It's reproducible that on the 2nd resume from suspend the sound fails to go to the headphones when they are connected and remains coming out of the speakers.

My alsa info output..

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

In Jaunty, please run "apport-collect 101986" without quotes, and let it pull in the required information. This should help in debugging the problem. Thank you.

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups:

I've run that.

Regards
mark

On Thu, 2009-06-04 at 09:46 +0000, Teej wrote:

> apport-collect 101986

Setting Triaged, Low. There should be enough information now so I'll let the developers handle this from here. If they need any more information do not hesitate to supply it to them. Thank for reporting this.

You should actually run apport-collect -p alsa-base 101986

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mark 3170 F.... mixer_applet2
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 22'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
DistroRelease: Ubuntu 9.04
Package: alsa-base 1.0.18.dfsg-1ubuntu8
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Just wanted to add that i have the same problem on Debian Lenny, with custom 2.6.30-rc2 kernel. After fresh reboot everything works, after resume headphone output is not functionall, sound is going throught internal speaker.

I have the same problem, Thinkpad X41 Tablet with Jaunty, after suspending even once all sound is emitted through the internal speakers, headphones are completely ignored (as in, no sound at all). Rebooting or hibernating to disk/resuming fix the issue.

Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D4p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 22'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
DistroRelease: Ubuntu 9.04
Package: alsa-base 1.0.18.dfsg-1ubuntu8
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_CA.UTF-8
Uname: Linux 2.6.28-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

I forgot to add in my comment #39 that problem is with IBM Thinkpad X41 Tablet. I yestarday installed 2.6.31-rc6 and will test it on Debian Lenny.

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: neresis 2030 F.... pulseaudio
 /dev/snd/pcmC0D0p: neresis 2030 F...m pulseaudio
 /dev/snd/pcmC0D0c: neresis 2030 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc8100000 irq 16'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,103c30c2,00100200 HDA:11c11040,103c1378,00100200'
   Controls : 11
   Simple ctrls : 9
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

I can confirm that I have the exact same problem with the headphones jack. After a fresh reboot it continue to work after a suspend-to-ram/wake-up cycle, but after sleeping/waking the second time it stops working. I find it curious that it works at all (after the first cycle) rather than just either working or not working at all.

My laptop is a Thinkpad X41 (non-tablet version). To be specific, I'm using the snd-intel8x0 driver, *not* the snd-hda-intel driver. Currently running Jaunty.

Through searching I have found this: https://lists.ubuntu.com/archives/kernel-team/2006-March/000699.html

There is no mention of *why* it needs to be blacklisted. Is it possible that due to changes in the past 3+ years this blacklisting is no longer necessary? At one point I pulled down the alsa source and trying to grok it for some sort of obvious error, but I couldn't make heads or tails of it.

My suspicion is that this is a hardware/driver issue. The kernel isn't issuing any errors or warnings, so maybe after waking up the second time some module isn't sending the right messages/flipping the right bits with respect to the hardware?

On Fri, Oct 16, 2009 at 6:40 PM, Brandon Sandrowicz <email address hidden> wrote:
> Through searching I have found this: https://lists.ubuntu.com/archives
> /kernel-team/2006-March/000699.html
>
> There is no mention of *why* it needs to be blacklisted. Is it possible
> that due to changes in the past 3+ years this blacklisting is no longer
> necessary?  At one point I pulled down the alsa source and trying to
> grok it for some sort of obvious error, but I couldn't make heads or
> tails of it.

Well, I'll explain here (that's my patch):

Many of those AD19xxB codecs erroneously expose X Jack Sense mixer
elements via the driver. You have to disable them (or mute them using
alsamixer if they're exposed) to get ANY audible analog output. As far
as I know, that remains the case and is completely orthogonal to your
issue, BUT I can't tell without seeing the contents of your
/proc/asound/card*/*codec*/* before and after the second suspend.

I'll look into getting you that output sometime this weekend.

After a fresh reboot.

The volume had been previously muted, so I unmuted it and turned it up so I could here my test mp3 through vlc. (note that I axed VLC before each sleep-wake cycle just in case access to the driver was the cause, but pulse audio was still running so I don't think that it would have mattered without shutting down pulse audio)

I got an empty 'diff -U10' between this one and the previous one.

Here is the output of 'diff -U10 /home/bjs/Desktop/1-after-first-sleep-wake-cycle.txt ~/Desktop/2-after-second-sleep-wake-cycle.txt':

--- /home/bjs/Desktop/1-after-first-sleep-wake-cycle.txt 2009-10-17 20:22:43.000000000 -0700
+++ /home/bjs/Desktop/2-after-second-sleep-wake-cycle.txt 2009-10-17 20:27:01.000000000 -0700
@@ -23,21 +23,21 @@
  PCM front DAC : 44100Hz
  PCM ADC : 44100Hz

  AD18XX configuration
  Unchained : 0x1000,0x0000,0x0000
  Chained : 0x0000,0x0000,0x0000
 /proc/asound/card0/codec97#0/ac97#0-0+regs:
  0:00 = 0090
- 0:02 = 0b0b
+ 0:02 = 0909
  0:04 = 0505
  0:06 = 0006
  0:08 = 0000
  0:0a = 0000
  0:0c = 801f
  0:0e = 801f
  0:10 = 9f9f
  0:12 = 0606
  0:14 = 0000
  0:16 = 9f9f

Looks like one of the registers was changed.

is there any way for me to cat something to ac97#0-0+regs to flip that value back and see if it 'magically' works?

After a little more digging, answered my own question. I would need to recompile the kernel with ALSA debugging enabled to be able to mess with the registers.

[Source] Search for "AC97 Sound" here: http://wiki.enneenne.com/index.php/WR1100's_devices_management_&_testing

Just discovered that suspend-to-disk 'fixes' this (headphones start working again) but it immediately stops working again after the first suspend-to-ram that I do (unlike from a fresh boot).

I'm suspecting something like Bug 151111 might be at fault. I tried to follow the directions for compiling the modules against the current kernel, but ended up with a 'invalid module format' when trying to insert them. I had to revert to my previous stock copies.

Why the initial s2ram after a fresh boot works is still up in the air, but it seems like this could be an issue with powering something down/up that gets lost and a complete power down/up of the system is needed (cold boot/reboot/s2disk) to reset it.

I have the same problem with a Thinkpad x41 tablet and Ubuntu 9.04.

As hibernating fixes the problem till the next suspend, I swapped off my swap partition to prevent the complete hibernating and the complete power down.

Hibernating still fixes the problem without a power down.
the contents in /proc/asound/card*/*codec*/* aren't being changed during the not-complete hibernating
this means that changing the values of the registers wont be the solution of the problem.

I can't follow what is the difference between a suspend/resume and a not-complete hibernating for the hardware or the kernel module.

inspecting the kernel messages doesn't show strange behavior between suspend/resume and not-complete hibernating thus the headphone jack is working (and repaired) after hibernating and not functional after the suspend/resume !

> I can't follow what is the difference between a suspend/resume and a
> not-complete hibernating for the hardware or the kernel module.

Not sure, but I'm sure that preparing for a s2disk is quite different
than a s2ram since the kernel shuts down (as the computer is
completely off) and dumps its state to disk.

If I have some time I'll look at the alsa code, but last time I
attempted to do so I couldn't make heads or tails of it which is why
I'm hoping someone knowledgeable can help out on this issue.

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: neresis 2578 F.... pulseaudio
 /dev/snd/pcmC0D0p: neresis 2578 F...m pulseaudio
 /dev/snd/pcmC0D0c: neresis 2578 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc8100000 irq 16'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,103c30c2,00100200 HDA:11c11040,103c1378,00100200'
   Controls : 11
   Simple ctrls : 9
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=4942587a-1056-4037-abe1-080d186fabdf
MachineType: Hewlett-Packard HP Compaq 6715s (GR654EA#ACB)
NonfreeKernelModules: wl
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=33799637-3cac-44df-85ac-917321d52153 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 07/16/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YTT Ver. F.07
dmi.board.name: 30C2
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.28
dmi.chassis.asset.tag: CNU7410LWD
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68YTTVer.F.07:bd07/16/2007:svnHewlett-Packard:pnHPCompaq6715s(GR654EA#ACB):pvrF.07:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.28:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6715s (GR654EA#ACB)
dmi.product.version: F.07
dmi.sys.vendor: Hewlett-Packard

@neresis Are you sure this is the same bug involving the same
hardware? If in doubt, please file a separate bug.

Your Ubuntu version is EOL. Does this still happen under supported Ubuntu versions?

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]