public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel Options: To use MSI-X or not?
Date: Wed, 04 Nov 2009 18:04:08 -0600	[thread overview]
Message-ID: <4AF21678.5020107@gmail.com> (raw)
In-Reply-To: <14754.1257356211@turing-police.cc.vt.edu>

On 11/04/2009 11:36 AM, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 04 Nov 2009 11:53:18 EST, Justin Piszcz said:
>
>> Example, 3ware cards/Intel Audio Drivers you can use MSI-X instead of
>> having several devices use/share an interrupt.
>>
>> What are the pros/cons to using MSI-X vs. having devices share an IRQ?
>
> Cons: Sometimes, you'll find a device that claims to support MSI but in fact is
> to some extent borked...
>
> I'm the proud owner of a Dell Latitude D820, which includes this PCI:
>
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
>          Subsystem: Dell Device 01cc
>          Flags: bus master, fast devsel, latency 0, IRQ 30
>          Memory at efffc000 (64-bit, non-prefetchable) [size=16K]
>          Capabilities: [50] Power Management version 2
>          Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
>          Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
>          Capabilities: [100] Virtual Channel<?>
>          Capabilities: [130] Root Complex Link<?>
>          Kernel driver in use: HDA Intel
>
> However, actually trying to enable MSI gets me this at some pseudo-random
> time after booting (one for each of 7 boots):
>
> [    4.519264] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0900
> [   22.788015] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x008f0c00
> [    4.719263] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0900
> [   12.497263] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0900
> [  815.350265] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0900
> [  595.171267] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00171700
> [    4.968263] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0900
>
> (Am slightly mystified about the resets at 4 and 12 seconds - at that point,
> we're not up far enough to actually try to use the audio. I suspect udev trying
> to initialize the card - except sometimes it works and runs just fine with
> MSI for quite some time:
>
> [14267.701267] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0900
> [12841.892050] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0900
> [10647.783274] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x001f1500
> [15091.102034] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00171700
> [20085.955293] ALSA sound/pci/hda/hda_intel.c:683: No response from codec, disabling MSI: last cmd=0x00df0700

This may not be an actual MSI problem (in fact I'd say it's probably 
not). Currently hda_intel disables MSI after any codec response timeout, 
so it could be it would have worked if it retried while still using MSI. 
I believe Takashi was going to change the driver to be less sensitive 
about this.

  reply	other threads:[~2009-11-05  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 16:53 Kernel Options: To use MSI-X or not? Justin Piszcz
2009-11-04 17:36 ` Valdis.Kletnieks
2009-11-05  0:04   ` Robert Hancock [this message]
2009-11-05  0:05 ` Robert Hancock

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=4AF21678.5020107@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    /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