From: Stephen Hemminger <shemminger@osdl.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Greg KH <greg@kroah.com>, Andi Kleen <ak@suse.de>,
linux-pci@atrey.karlin.mff.cuni.cz, acurrid@nvidia.com,
amartin@nvidia.com, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: MSI failure on Nvidia nForce
Date: Tue, 18 Apr 2006 11:48:44 -0700 [thread overview]
Message-ID: <20060418114844.49f79773@localhost.localdomain> (raw)
In-Reply-To: <444531F8.3040109@garzik.org>
On Tue, 18 Apr 2006 14:37:44 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> Stephen Hemminger wrote:
> > I got a report of sky2 driver irq test failing on x86_64 using
> > the following configuration. Is this a known problem?
> > Should workaround be done at PCI layer?
> >
> > What the driver does is setup MSI handler, then do a software generated
> > IRQ and check that it was received (similar to tg3). If IRQ test fails
> > it falls back to INTx.
>
> Please describe precisely -how- it fails.
>
> pci_enable_msi() does not fail properly on systems that do not support
> MSI. This is a major unresolved problem that is preventing MSI
> deployment, and causing every driver writer to include a does-MSI-work
> test in their driver.
>
> We need to find a good generic test, or if that fails, adopt an
> ACPI-like rule: whitelist systems with working MSI before $X date, and
> blacklist systems with broken MSI after $X date.
>
> Jeff
>
The message from the driver reported was:
> I'me currently getting a lot of hang up with my computer (x86_64,
> ati,...). I've saw this message in my dmesg :
>
> sky2: 0000:02:00.0: No interupt was generated using MSI, switching to
> INTx mode. Please report this failure to the PCI maintener and include
> system chipset information.
Which means that. pci_enable_msi succeeded, but the IRQ routing was
screwed up.. There maybe more of a BIOS problem on this system because
the IRQ is showing up as edge triggered as well. Edge triggered interrupts
don't work with NAPI.
cat /proc/interrupts
CPU0
0: 333581 IO-APIC-edge timer
1: 1461 IO-APIC-edge i8042
2: 0 XT-PIC cascade
7: 2 IO-APIC-edge ehci_hcd:usb1, NVidia CK804
8: 0 IO-APIC-edge rtc
9: 0 IO-APIC-edge acpi
10: 55872 IO-APIC-edge sky2
11: 21025 IO-APIC-edge libata
15: 49 IO-APIC-edge ide1
NMI: 587
LOC: 333569
ERR: 0
MIS: 0
prev parent reply other threads:[~2006-04-18 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060418111944.6ed0505e@localhost.localdomain>
2006-04-18 18:37 ` Jeff Garzik
2006-04-18 18:48 ` Stephen Hemminger [this message]
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=20060418114844.49f79773@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=acurrid@nvidia.com \
--cc=ak@suse.de \
--cc=amartin@nvidia.com \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
Powered by JetHome