From: Takashi Iwai <tiwai@suse.de>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: snd_hda_intel 2.6.24-rc2 bug: interrupts don't always work on Lenovo X60s
Date: Wed, 14 Nov 2007 14:33:34 +0100 [thread overview]
Message-ID: <s5hejetdk9d.wl%tiwai@suse.de> (raw)
In-Reply-To: <adawsskzqr9.fsf@cisco.com>
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
next prev parent reply other threads:[~2007-11-14 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 22:48 snd_hda_intel 2.6.24-rc2 bug: interrupts don't always work on Lenovo X60s Roland Dreier
2007-11-12 7:39 ` Takashi Iwai
2007-11-12 16:59 ` Roland Dreier
2007-11-12 13:41 ` Takashi Iwai
2007-11-12 18:46 ` Roland Dreier
2007-11-13 3:43 ` Takashi Iwai
2007-11-14 16:39 ` Roland Dreier
2007-11-14 13:19 ` Takashi Iwai
2007-11-14 17:22 ` Roland Dreier
2007-11-14 13:33 ` Takashi Iwai [this message]
2007-11-22 17:42 ` Theodore Tso
2007-11-23 7:06 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hejetdk9d.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.