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: <s5hwssnvaw1.wl%tiwai@suse.de>
Date:	Mon, 12 Nov 2007 14:41:50 +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 Mon, 12 Nov 2007 08:59:49 -0800,
Roland Dreier wrote:
> 
>  > You seem to pass unneeded module options to snd-hda-intel driver like
>  > MSI enablement.  First, try to remove all these options.
> 
> Yes, it's trivial to reproduce without any options:
> 
>     [ 2311.759856] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21
>     [ 2311.759866] hda_intel: probe_mask set to 0x1 for device 17aa:2010
>     [ 2311.759886] PCI: Setting latency timer of device 0000:00:1b.0 to 64
>     [ 2312.911309] hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x003f000c

Hm, strange, NID 0x03 shouldn't be accessed via AD1981 codec, at
least, thinkpad model.  Did you enable CONFIG_SND_HDA_CODEC_ANALOG?
Otherwise it won't work.

> (By the way, what's wrong with using the enable_msi option?  MSI seems
> very solid on Intel platforms, and I prefer avoiding shared interrupts)

It may work, but first we need to make sure that we're seeing the same
problem.  MSI is one of the unstable factors for many platforms, thus
the driver tries to disable MSI first if any sign of wrong irqs is
found.


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/