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: Mon, 12 Nov 2007 14:41:50 +0100 [thread overview]
Message-ID: <s5hwssnvaw1.wl%tiwai@suse.de> (raw)
In-Reply-To: <adak5on2yd6.fsf@cisco.com>
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
next prev parent reply other threads:[~2007-11-12 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 22:48 Roland Dreier
2007-11-12 7:39 ` Takashi Iwai
2007-11-12 16:59 ` Roland Dreier
2007-11-12 13:41 ` Takashi Iwai [this message]
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
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=s5hwssnvaw1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®