From: Ben Greear <greearb@candelatech.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard
Date: Wed, 23 Mar 2005 19:22:58 -0800 [thread overview]
Message-ID: <42423292.60701@candelatech.com> (raw)
In-Reply-To: <42421FF2.7050501@candelatech.com>
Ben Greear wrote:
> I'm having a strange problem. I have an X6DVA motherboard
> with dual 2.8Ghz emt-64 processors, 1GB of RAM, SATA HD, etc.
> I tried kernel 2.6.11 which uses irq 26, and 2.6.10-1.770_FC2smp, which
> maps the irq to 209 or something like that. Distribution is FC2, x86.
> Kernel is compiled for x86-SMP as well.
>
> I suspect that this may be a hardware issue of some sort, but if anyone
> has any suggestions as to how to debug this further, please do let
> me know. I'm attaching the lspci and dmesg output in case that helps.
I am now less certain: I tried with a separate but similar machine, and
eth3 still has bad interrupt test. I tried 2.6.9 kernel, same problem.
I tried 2.4.29 kernel (on FC2 distribution), and the same problem exists.
I tried with pci=noacpi, and this just messes up everything (irqs are
disabled, etc).
Could this be a bug in the motherboard implementation?
Off to try some different combinations of NIC hardware...
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-03-24 3:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 2:03 PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard Ben Greear
2005-03-24 3:22 ` Ben Greear [this message]
2005-03-24 8:10 ` Lennert Buytenhek
2005-03-24 8:18 ` Ben Greear
2005-03-24 19:38 ` Ben Greear
2005-03-29 20:36 ` PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard (Solved) Ben Greear
2005-04-14 18:01 ` PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard Ganesh Venkatesan
2005-04-14 20:34 ` Ben Greear
2005-03-24 10:13 ` Daniel Egger
2005-03-24 18:07 ` Ben Greear
2005-03-24 18:29 ` Francois Romieu
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=42423292.60701@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).