linux-kernel - Re: 2.6.18: hda_intel: azx_get_response timeout, switching to single

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Sep 2006 12:16:33 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Pavel Machek <pavel@...e.cz>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	alsa-devel@...a-project.org, Andrew Morton <akpm@...l.org>
Subject: Re: 2.6.18: hda_intel: azx_get_response timeout, switching to single_cmd mode...

At Mon, 25 Sep 2006 12:58:08 -0700,
Jeremy Fitzhardinge wrote:
> 
> 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.
> 

There is no big change relevant to TP X60 during 2.6.18rc, so I don't
think it's a regression in the hd-audio driver code.

> Details attached.  The dmesg output is for the FC6 distro kernel 
> 2.6.18-1.2689.fc6PAE, but I see the same symptoms with 2.6.18-mm1.

You must see difference with mm1 (suppose that mm1 already includes
the latest ALSA patches).  When the CORB/RIRB interrupt gets broken,
the driver first switches to poling mode, then single_cmd mode as
fallback.

Also, try disable_msi=1 option for mm1.  MSI seems broken on some
systems.


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