Date: Tue, 10 Nov 2009 17:43:56 +0100
Message-ID: <s5hy6mel48j.wl%tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: bdale@gag.com (Bdale Garbee)
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with codec discovery on HP 2530p
In-Reply-To: <20091110145338.A55E719D7AD@rover.gag.com>
References: <20091110145338.A55E719D7AD@rover.gag.com>
User-Agent: Wanderlust/2.15.6 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.7 Emacs/23.1
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
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
Content-Length: 2052
Lines: 52

At Tue, 10 Nov 2009 09:53:38 -0500 (EST),
Bdale Garbee wrote:
> 
> I recently moved from 2.6.30.9 to the 2.6.32-rcX series on my HP EliteBook 
> 2530p.  Audio didn't work, and I've finally made time to track down the 
> problem.  It turns out the problem actually started with 2.6.31-rc1, due
> to a patch that was part of the 2.6.30-rcX series but apparently wasn't in
> the 2.6.30 stable release.  
> 
> The symptom is:
> 
> HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> HDA Intel 0000:00:1b.0: irq 30 for MSI/MSI-X
> HDA Intel 0000:00:1b.0: setting latency timer to 64
> hda-intel: Codec #0 probe error; disabling it...
> hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
> hda-intel: no codecs initialized
> hda-intel: spurious response 0x0:0x0, last cmd=0x0f0000
> HDA Intel 0000:00:1b.0: PCI INT A disabled

Hm, looks like the codec communication got screwed up by some reason.

> The codec in this machine is an AD1984A.  Bisecting, I discovered that 
> reverting this single commit fixes things for me in 2.6.32-rc6:
> 
> 8174086167d43d0fd7b21928074145ae1d15bbab is the first bad commit
> commit 8174086167d43d0fd7b21928074145ae1d15bbab
> Author: Takashi Iwai <tiwai@suse.de>
> Date:   Tue May 26 15:22:00 2009 +0200
> 
>     ALSA: hda - Allow concurrent RIRB access in single_cmd mode

This commit itself is unlikely relevant, I guess.
It's only for single-cmd mode, which is the last fallback if the
codec communication fails.  That is, if this change does have any
influence, it means that the device is already in a weird status.

Could you give alsa-info.sh output (run with --no-upload option)
on the working (2.6.30.x) kernel?

Also, what module options do you give to snd-hda-intel?


thanks,

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