[Dell Studio 1458] No sound after suspend (Ubuntu 12.10 64bit)

[mlaverdiere]

Since the beginning of my experience with 12.10 beta, I have repeated problems with the sound. Lately (beta 2, kernel 3.5.0.17.19), the problem is that after initial boot, sound works fine, but after suspend-resume, sound stops working. I'm using a Dell Studio 1458 laptop with the following audio card (according to lspci): Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05).

WORKAROUND: disabling auto-mute in alsamixer.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ml 2262 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sat Oct 13 13:39:14 2012
HibernationDevice: RESUME=UUID=319bc80d-8569-4015-bf0f-543ab8880a47
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Studio 1458
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=6a5e8117-9e80-4434-afe5-757912b691e1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: Upgraded to quantal on 2012-09-28 (14 days ago)
dmi.bios.date: 05/12/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 056DH9
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/12/2011:svnDellInc.:pnStudio1458:pvrA07:rvnDellInc.:rn056DH9:rvrA07:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Studio 1458
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

[penalvch (penalvch)]

mlaverdiere, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

As well, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

[mlaverdiere (mlaverdiere)]

As requested, see the dmesg.txt file attached, created with the DebuggingKernelSuspend procedure (with 3.5.0.17.19 kernel).

Also, I've tested the latest mainline kernel (3.6.2) and it's even worst, i.e. there's no sound at all after first boot within Unity/Gnome, but there is sound at lightdm stage.. This makes me think that this might not be a kernel bug but rather a Unity/Gnome bug. Should this bug report linked to a different package then?

[penalvch (penalvch)]

mlaverdiere, thank you for providing the file and testing the newest mainline. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066353/comments/3 :
>"...but there is sound at lightdm stage.. This makes me think that this might not be a kernel bug but rather a Unity/Gnome bug. Should this bug report linked to a different package then?"

Not at this point.

Did this problem not occur in a release prior to Quantal?

[mlaverdiere (mlaverdiere)]

Sound was working fine for me with 12.04 and previous versions. The problem did start with Quantal.

[penalvch (penalvch)]

mlaverdiere, the next step is to perform a kernel bisect from Precise to Quantal kernel 3.5.0.17.19, in order to identify the offending commit(s). Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[mlaverdiere (mlaverdiere)]

I don't have too much time right now but I did the test with previous kernels 3.2 (leftover from Precise) and 3.4 and here's the results:

- 3.2: sound works fine, even after many suspends
- 3.4: system hangs at lightdm stage (no response at all), just before the usual Ubuntu sound theme is played it seems.

I also tried to with gdm + gnome-shell (so no lightdm and no Unity), and the problem still occurs with the Quantal kernel.

[mlaverdiere (mlaverdiere)]

I did other tests with kernels in mainline, and here's the results:

-with all Quantal kernel 3.5 and below, sound works fine (including 3.5.0-030500)
-with Quantal kernel 3.6.2 kernel, sound is not working

Otherwise, I've tested the regular (as provided in official repository) 3.5.0-17 kernel with KDE (so nothing from Unity/Gnome loaded), and the problem is also occurring.

[hdante (hdante)]

I have the same problem (audio stops working after suspend=>resume), but on different hardware (iMac 9,1).

[penalvch (penalvch)]

hdante, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

[Michael Frick (mdfrick)]

I had similar issues with sound disappearing for seemingly no reason (sometimes due to suspend-resume, sometimes from docking) after upgrading from 12.04 to 12.10 on my ThinkPad T430s - also Intel audio, though mine is listed as "Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)".

After finding this answer at AskUbuntu:
http://askubuntu.com/questions/203312/how-come-my-sound-wont-work-on-lenovo-thinkpad-x230

- I've gotten sound working again. Just open up alsamixer from a terminal and disable Auto-Mute (right arrow to highlight, down arrow or minus key to disable). Worth a shot if you haven't tried it yet, I had played with various settings in alsamixer prior to finding this, but had never thought to disable something as innocuous as Auto-Mute. Sound had even stopped working at the point that I'd found this and immediately began working again after disabling Auto-Mute. Hopefully something this simple helps your situation as well.

[mlaverdiere (mlaverdiere)]

I confirm Michael (#11) observation: disabling auto-mute in alsamixer solves the problem, with official kernel (actually 3.5.0-17-generic).

My understanding is that auto-mute is for turning off speakers when headphones are plugged in. So if speakers are turned off after suspending (or even after loging in, as the current behaviour is inconsistent), this is still a bug to be fixed.

[Mikael Strom (mikael-sesamiq)]

I have the same problem on MPB 5,1. Disable auto-mute resolves the problem.

[hdante (hdante)]

Quick testing with auto-mute in alsamixer resulted in the following behavior:

1) before using alsa mixer, after a suspend-resume, audio didn't work
2) enter alsamixer, auto-muted was enabled
3) set auto-muted to disabled, random "synthetic-fart" noise
4) open browser, go to youtube, turn up the volume and audio works
5) set auto-muted to enabled, audio stops working
6) set auto-muted to disabled audio resumes
7) stop music, suspend, resume, audio keeps working

Just for completenes, my machine is an iMac 9,1.
Relevant modules:
snd_hda_codec_realtek 77876 1
snd_hda_intel 33491 5
snd_hda_codec 134212 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 13602 1 snd_hda_codec
snd_pcm 96580 3 snd_hda_intel,snd_hda_codec
snd_seq_midi 13324 0
snd_rawmidi 30512 1 snd_seq_midi
snd_seq_midi_event 14899 1 snd_seq_midi
snd_seq 61521 2 snd_seq_midi,snd_seq_midi_event
snd_timer 29425 2 snd_pcm,snd_seq
snd_seq_device 14497 3 snd_seq_midi,snd_rawmidi,snd_seq
snd 78734 18 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 15047 1 snd
snd_page_alloc 18484 2 snd_hda_intel,snd_pcm

I'm marking this bug as affecting me.

[Rubeosis (faspie)]

I have the same problem with a Dell XPS One 27 on Ubuntu 13.04 Raring AMD64

[penalvch (penalvch)]

Rubeosis / Mikael Strom / Michael Frick, if you have a bug in Ubuntu, the Ubuntu Audio Developer team, Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad all would like you to please file a new report by executing the following in a terminal:
ubuntu-bug sound

For more on this, please see the Ubuntu Audio Developer team article:
https://wiki.ubuntu.com/DebuggingSoundProblems

the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

hdante, please see the comment already posted to you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066353/comments/10 .