Bug 24052 - hda-intel: broken capture after azx_get_response timeout
Summary: hda-intel: broken capture after azx_get_response timeout
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-29 21:48 UTC by cthx
Modified: 2015-02-19 16:03 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.36.1
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description cthx 2010-11-29 21:48:08 UTC
audio capture stops after this messages:

hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x003f0600
hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x003f0600

HP Compaq 6715b
Archlinux x86_64


lspci:
00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge
00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx)
00:04.0 PCI bridge: ATI Technologies Inc Device 7914
00:05.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 1)
00:06.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 2)
00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA
00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0)
00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1)
00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2)
00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3)
00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4)
00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI)
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14)
00:14.1 IDE interface: ATI Technologies Inc SB600 IDE
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series]
02:04.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b6)
02:04.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 02)
10:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
30:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 02)
Comment 1 Takashi Iwai 2010-11-30 08:26:05 UTC
Is this a regression from the old kernel?
Comment 2 cthx 2010-11-30 19:39:45 UTC
I think it's a regression, but not sure.
I've downgraded kernel to 2.6.25.8, testing now.

First I have capture problems,after that I see dmesg messages.
This problem appears randomly, after reboot capture is ok.
Comment 3 cthx 2010-11-30 19:55:48 UTC
Seems problem exist for 2.6.35.8 too (25 was typo :))
capture randomly stops, but without dmesg messages.
Comment 4 cthx 2010-11-30 21:25:05 UTC
steps to reproduce: i have open audio player (amarok)
and open and close mumble or audacity :).
after some steps (opening-closing apps with audio capturing) capture is down.
Comment 5 Takashi Iwai 2013-11-19 09:01:57 UTC
Does the problem still happen with 3.12 kernel?
Comment 6 cthx 2013-11-19 10:17:37 UTC
I've forgotten about this bug :) Now I have another (intel-based) laptop and here seems this bug not appears (at least with 3.12). I can test later my old laptop ( ~1.5 weeks later ).
Comment 7 Takashi Iwai 2013-11-29 07:54:50 UTC
OK, if it's still a problem, please give alsa-info.sh output.  Run it with --no-upload option, and attach the output to bugzilla.
Comment 8 cthx 2013-12-27 22:01:19 UTC
Sorry for the late answer, I've tested my old laptop recently with 3.12.6 kernel and I couldn't reproduce this bug. I think the bug can be closed :)

Note You need to log in before you can comment on or make changes to this bug.