From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, erich <erich@areca.com.tw>,
Arjan van de Ven <arjan@infradead.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
billion.wu@areca.com.tw, akpm@osdl.org, oliver@neukum.org
Subject: Re: Areca RAID driver remaining items?
Date: Fri, 24 Feb 2006 09:03:47 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0602240858180.7894@shark.he.net> (raw)
In-Reply-To: <20060224165647.GA4176@infradead.org>
On Fri, 24 Feb 2006, Christoph Hellwig wrote:
> On Thu, Feb 23, 2006 at 11:59:50AM +0000, Alan Cox wrote:
> > On Iau, 2006-02-23 at 17:50 +0800, erich wrote:
> > > But unfortunately I found some mainboards will hang up if I always enable
> > > this function in my lab.
> > > To avoid this issue, I do an option for this case.
> > >
> > > But Christoph Hellwig give me comment with it.
> >
> >
> > Another thing you can also do for many of these cases is to use either
> > the PCI or DMI interfaces to identify the problem board and
> > automatically set the option as well.
> >
> > There are two ways to do this. One is
>
> Please avoid that unless really nessecary. I doubt there's boards where
> MSI would only be broken with the areca card but not with other MSI-capable
> ones. If a board or chipset is generally broken vs MSI it should be
> added to the global MSI blacklist. It's probably be nice to have a global
> nomsi boot option instead of one in every driver aswell..
Jeff G. added an "msi" option to the sata_mv driver recently.
But yes, I expect it to be more of a platform issue than a
driver issue.
s2io network people report MSI interrupt problems on various
platforms (on netdev mailing list).
There are other reports (that I have at home, not visible to me
now). It would be good to have an MSI expert around.
http://www.xenotime.net/linux/patches/pci_nomsi.patch adds a
global boot option to disable MSI interrupt assignments.
--
~Randy
next prev parent reply other threads:[~2006-02-24 17:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 18:02 Areca RAID driver remaining items? Dax Kelson
2006-02-20 18:11 ` Arjan van de Ven
2006-02-20 18:20 ` Christoph Hellwig
2006-02-22 6:27 ` erich
2006-02-22 14:57 ` Christoph Hellwig
2006-02-23 6:27 ` erich
2006-02-23 8:25 ` Arjan van de Ven
2006-02-23 9:50 ` erich
2006-02-23 9:56 ` Arjan van de Ven
2006-02-23 11:51 ` erich
2006-02-23 12:07 ` Arjan van de Ven
2006-02-24 2:08 ` erich
2006-02-24 8:50 ` Arjan van de Ven
2006-02-23 11:59 ` Alan Cox
2006-02-24 2:36 ` erich
2006-02-24 16:56 ` Christoph Hellwig
2006-02-24 17:03 ` Randy.Dunlap [this message]
2006-02-24 19:38 ` Matthew Wilcox
2006-02-24 20:14 ` Randy.Dunlap
2006-02-26 6:41 ` Randy.Dunlap
2006-02-26 16:02 ` Matthew Wilcox
2006-02-26 19:00 ` Randy.Dunlap
2006-02-24 3:18 erich
2006-02-27 11:27 erich
2006-02-27 12:36 ` Matthew Wilcox
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=Pine.LNX.4.58.0602240858180.7894@shark.he.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=billion.wu@areca.com.tw \
--cc=erich@areca.com.tw \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=oliver@neukum.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;
as well as URLs for NNTP newsgroup(s).