Issues with sound on intel-hda in Edgy (2.6.17)

Bug #69620 reported by sog
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: linux-generic

The intel-hda driver appears to have significant issues in both Dapper and Edgy. To be more specific, this is a good description of what I'm experiencing (taken from the thread here (http://www.ussg.iu.edu/hypermail/linux/kernel/0609.3/0467.html)):

"I have a ThinkPad X60 which uses the Intel 82801G HDA audio chip. This used to work for me, but lately (sometime during 2.6.18-rcX series) it stopped working - programs trying to use it tend to just block forever waiting for /dev/dsp.

The only obvious symptom is:

hda_intel: azx_get_response timeout, switching to single_cmd mode...

appearing in the kernel log when booting."

It's particularly bad post-suspend, but occurs intermittently otherwise. I'm also on an X60s. See confirmation from another Ubuntu user here (http://www.ubuntuforums.org/showthread.php?t=156146&highlight=hda_intel%3A+azx_get_response).

Revision history for this message
Daniel T Chen (crimsun) wrote :

The majority of the issues causing said symptom have been fixed in alsa-kernel hg. Patches were available in early October and have been backported to both Dapper and Edgy linux-source (see the October '06 Ubuntu kernel-team list archives) but have yet to be merged (note that some said patches are invasive and questionable for an LTS release).

Two additional points:
1) Make sure you're running the latest BIOS;
2) Try compiling alsa-driver 1.0.13 from upstream alsa-project.org.

Changed in linux-meta:
status: Unconfirmed → Fix Committed
Revision history for this message
Sebastian Wiesinger (sebastianw) wrote :

I found another reason for this bug.

I use a Thinkpad T60, and as stated on thinkwiki, I added pci=noacpi, acpi_sleep=s3_bios to my kernel to enable suspend mode. After removing this from my grub options and rebooting, the sound worked fine again.

The problems started after the first time suspending the system, but didn't go away after multiple reboots.

Revision history for this message
Matthew Garrett (mjg59) wrote :

Please don't add random kernel options and then expect things to work anyway. Neither of those options are required for suspend on Ubuntu, and pci=noacpi is very likely to break things.

Revision history for this message
Sebastian Wiesinger (sebastianw) wrote :

I know, but suspend worked after doing these changes, so I was satisfied. And without them, my sound/network works, but suspend is broken...

Changed in linux-source-2.6.17:
importance: Undecided → Medium
Revision history for this message
Fabián Rodríguez (magicfab) wrote :

This seems related to bug #49439

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This report was marked 'Fix Committed' a while ago and there hasn't been any activity in it recently. I'm going to go ahead and mark the status as 'Fix Released'. If this is not the case, please retest against the latest Hardy Alpha release and report back your results. Thanks in advance.

Changed in linux-source-2.6.17:
status: Fix Committed → Fix Released
Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

The behaviour described in the initial report can be seen on Asus EeePC 1101HA on latest Karmic. The bug is NOT fixed so far.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.