From: Jay Cliburn <jacliburn@bellsouth.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Chuck Ebbert" <cebbert@redhat.com>,
"Tejun Heo" <htejun@gmail.com>, "Greg K-H" <greg@kroah.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Matías Alejandro Torres" <torresmat@gmail.com>
Subject: Re: [PATCH] pci-quirks: disable MSI on RS400-200 and RS480, take #2
Date: Wed, 09 May 2007 15:52:07 -0500 [thread overview]
Message-ID: <46423477.2080509@bellsouth.net> (raw)
In-Reply-To: <46421FCA.7010807@garzik.org>
Jeff Garzik wrote:
> Chuck Ebbert wrote:
>> Tejun Heo wrote:
>>>> FWIW several distros have turned off MSI by default and added
>>>> a "pci=msi" option to enable it.
>>> Yeah, it seem to cause a lot of problems on certain chips but I think
>>> the correct path is to add PCI quirks for those. Most MSI problems I've
>>> seen are on these ATI chips. Do you happen to know any other?
>>
>> We had devices that didn't do MSI right, e.g. forcedeth and others I
>> can't recall now.
>
> AFAIK that's a broken diagnosis. It's the system, not the device, that
> is problematic.
>
In the case of the Attansic L1 ethernet driver, here's what we see:
chipset kernel arch MSI functionality
=============== =========== =================
Intel 945G/ICH7 x86_64 yes
Intel 945G/ICH7 i386 yes
Via K8T890 x86_64 yes
Via K8T890 i386 no
I still don't know why, but we get a flood of APIC errors after starting the
atl1 driver on a Via K8T890 board (Asus M2V, for example) under a 32-bit kernel,
and *only* under a 32-bit kernel.
http://lkml.org/lkml/2007/4/8/68
Supporting files and such at ftp://ftp.hogchain.net/pub/linux/m2v/apic-problem
Any hints heartily welcomed...
Jay
next prev parent reply other threads:[~2007-05-09 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 12:23 [PATCH] pci-quirks: disable MSI on RS400-200 and RS480, take #2 Tejun Heo
2007-05-09 15:37 ` Chuck Ebbert
2007-05-09 15:50 ` Tejun Heo
2007-05-09 15:56 ` Chuck Ebbert
2007-05-09 16:04 ` Tejun Heo
2007-05-09 19:23 ` Jeff Garzik
2007-05-09 20:52 ` Jay Cliburn [this message]
2007-05-19 12:13 ` Jay Cliburn
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=46423477.2080509@bellsouth.net \
--to=jacliburn@bellsouth.net \
--cc=cebbert@redhat.com \
--cc=greg@kroah.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torresmat@gmail.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