linux-kernel - Re: snd_hda_intel 2.6.24-rc2 bug: interrupts don't always work on Lenovo X60s

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]

Message-ID: <s5hejetdk9d.wl%tiwai@suse.de>
Date:	Wed, 14 Nov 2007 14:33:34 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Roland Dreier <rdreier@...co.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: snd_hda_intel 2.6.24-rc2 bug: interrupts don't always work on Lenovo X60s

At Wed, 14 Nov 2007 09:22:18 -0800,
Roland Dreier wrote:
> 
>  > NWhat cmd more exactly?  The below is GET_DIGI_CONVERT.  So it must be
>  > related with SPDIF but it must be same as 2.6.23.  Or do you happen to
>  > set CONFIG_SND_HDA_POWER_SAVE=y?
> 
> The new error message is:
> 
>     hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x002f0d00
> 
> so the cmd is 0x002f0d00.
> 
> I'm not sure if I ever saw this with 2.6.23 or not -- it is rare
> enough that I may have missed it.  I do have
> 
>     CONFIG_SND_HDA_POWER_SAVE=y
>     CONFIG_SND_HDA_POWER_SAVE_DEFAULT=5

First try to set power_save_controller=0 module option for
snd-hda-intel.  If this doesn't make any difference, try to turn
CONFIG_SND_HDA_POWER_SAVE off.  If the problem still persists, then I
have no idea what change triggered it.  Maybe you got this in the
earlier versions but in less verbose way...

> in my .config.  And I don't think that the X61s has anything
> SPDIF-related accessible on the outside... not sure what mmight be
> going on inside of course.

It's on the docking station, IIRC.


thanks,

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/