From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Dillow <dave@thedillows.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Adaptec 1420SA issues with MSI
Date: Tue, 17 Jan 2006 14:39:44 -0500 [thread overview]
Message-ID: <43CD4800.20604@pobox.com> (raw)
In-Reply-To: <20060109221323.65f6987d.akpm@osdl.org>
Andrew Morton wrote:
> Andi says "It's more likely a hardware bug that needs to be handled by the
> driver maintainer. sata_mv has an pci_enable_msi(). Hardware that reports
> MSI capability but breaks when it's actually used is not unheard of."
>
> -sata_mv 0000:00:0a.0: 32 slots 4 ports unknown mode IRQ via MSI
> -ata1: SATA max UDMA/133 cmd 0x0 ctl 0xE0A22120 bmdma 0x0 irq 177
> -ata2: SATA max UDMA/133 cmd 0x0 ctl 0xE0A24120 bmdma 0x0 irq 177
> -ata3: SATA max UDMA/133 cmd 0x0 ctl 0xE0A26120 bmdma 0x0 irq 177
> -ata4: SATA max UDMA/133 cmd 0x0 ctl 0xE0A28120 bmdma 0x0 irq 177
> +sata_mv 0000:00:0a.0: 32 slots 4 ports unknown mode IRQ via INTx
> +ata1: SATA max UDMA/133 cmd 0x0 ctl 0xE0A22120 bmdma 0x0 irq 18
> +ata2: SATA max UDMA/133 cmd 0x0 ctl 0xE0A24120 bmdma 0x0 irq 18
> +ata3: SATA max UDMA/133 cmd 0x0 ctl 0xE0A26120 bmdma 0x0 irq 18
> +ata4: SATA max UDMA/133 cmd 0x0 ctl 0xE0A28120 bmdma 0x0 irq 18
>
> It seems strange that pci_enable_msi() succeeded if the device is not
> MSI-capable?
See http://lkml.org/lkml/2006/1/17/145
pci_enable_msi() has a problem where it succeeds when it should not, but
also, sata_mv is still missing some errata workarounds that could be
affecting MSI platforms.
Jeff
next prev parent reply other threads:[~2006-01-17 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 21:06 Adaptec 1420SA issues with MSI Dave Dillow
2006-01-10 6:13 ` Andrew Morton
2006-01-10 6:31 ` Jeff Garzik
2006-01-17 19:39 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 4:53 Dave Dillow
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=43CD4800.20604@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=dave@thedillows.org \
--cc=linux-ide@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.