From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760071AbXKNR2U (ORCPT ); Wed, 14 Nov 2007 12:28:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752058AbXKNR2K (ORCPT ); Wed, 14 Nov 2007 12:28:10 -0500 Received: from mail.suse.de ([195.135.220.2]:45910 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751526AbXKNR2J (ORCPT ); Wed, 14 Nov 2007 12:28:09 -0500 Date: Wed, 14 Nov 2007 14:33:34 +0100 Message-ID: From: Takashi Iwai To: Roland Dreier Cc: linux-kernel@vger.kernel.org Subject: Re: snd_hda_intel 2.6.24-rc2 bug: interrupts don't always work on Lenovo X60s In-Reply-To: References: User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta28) (fuki) (+CVS-20070806) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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