Re: sound: azx_get_response timeout

[Takashi Iwai]

At Tue, 29 Apr 2008 12:31:47 +0200 (CEST),
Jan Engelhardt wrote:
> 
> 
> Out of the blue, sound stops and dmesg throws:
> 
> ALSA sound/pci/hda/hda_intel.c:596: hda_intel: azx_get_response timeout, 
> switching to polling mode: last cmd=0x000f0000

It's a warining and usually OK as long as you don't get errors with
single_cmd mode after this message.

> Kernel is 2.6.25-19-default (from opensuse 11.0beta1)
> Alsamixer says:
> 	Card: HDA VIA VT82xx
> 	Chip: VIA VIA VT1708
> lspci:
> 	02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio 
> 	Controller (rev 10)
(snip) 
> Messages from dmesg when reloading the module:
> ALSA sound/pci/hda/hda_codec.c:2860: autoconfig: line_outs=4 (0x1f/0x1c/0x22/0x23/0x0)
> ALSA sound/pci/hda/hda_codec.c:2864:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> ALSA sound/pci/hda/hda_codec.c:2868:    hp_outs=1 (0x20/0x0/0x0/0x0/0x0)
> ALSA sound/pci/hda/hda_codec.c:2869:    mono: mono_out=0x0
> ALSA sound/pci/hda/hda_codec.c:2877:    inputs: mic=0x1d, fmic=0x21, line=0x1e, fline=0x0, cd=0x24, aux=0x0
> hda_codec: num_steps = 0 for NID=0x1f (ctl = Front Playback Volume)
> hda_codec: num_steps = 0 for NID=0x1a (ctl = Center Playback Volume)
> hda_codec: num_steps = 0 for NID=0x19 (ctl = Side Playback Volume)
> hda_codec: num_steps = 0 for NID=0x20 (ctl = Headphone Playback Volume)
> hda_codec: num_steps = 0 for NID=0x15 (ctl = Capture Volume)

These look bad.  It seems that the codec doesn't provide any amp
information of the corresponding widgets although the driver tries to
create mixer elements with them.

What show /proc/asound/card0/codec#* files?

> The only way to get rid of the GETOSPACE=0 state is to reboot the
> machine. Say, could this be due to the crappy VIA hardware?

Possible.

You may try some module options for snd-hda-intel,
e.g. position_fix=0.  See ALSA-Configuration.txt.


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/