| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Mystery packet killing tg3 |
| From: | Stephen Hemminger <shemminger@xxxxxxxx> |
| Date: | Tue, 3 May 2005 14:29:52 -0700 |
| Cc: | jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20050503141314.441c9d75.davem@xxxxxxxxxxxxx> |
| Organization: | Open Source Development Lab |
| References: | <20050502162405.65dfb4a9@xxxxxxxxxxxxxxxxxxxxx> <20050502200251.38271b61.davem@xxxxxxxxxxxxx> <20050503140528.1bd2ac74@xxxxxxxxxxxxxxxxx> <20050503141314.441c9d75.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 3 May 2005 14:13:14 -0700 "David S. Miller" <davem@xxxxxxxxxxxxx> wrote: > On Tue, 3 May 2005 14:05:28 -0700 > Stephen Hemminger <shemminger@xxxxxxxx> wrote: > > > 00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) > > (prog-if 10 [IO-APIC]) > > Buggy 8131 APIC, does the drivers/pci/quirks.c:quirk_amd_8131_ioapic() > message: > > PCI: MSI quirk detected. pci_msi_quirk set. yes. that is there. > trigger? MSI support recently got added to the tg3.c driver, but it should > only register MSI interrupt handling if pci_enable_msi() returns zero. There is no call to pci_enable_msi in the 2.6.12-rc3 source > See what it ends up doing, or if you even have a MSI capable tg3.c in > your kernel. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Mystery packet killing tg3, David S. Miller |
|---|---|
| Next by Date: | Re: [IPV6] Fix raw socket checksums with IPsec, David S. Miller |
| Previous by Thread: | Re: Mystery packet killing tg3, David S. Miller |
| Next by Thread: | Re: Mystery packet killing tg3, Michael Chan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |