netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ganesh Venkatesan <ganesh.venkatesan@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "netdev@oss.sgi.com" <netdev@oss.sgi.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard
Date: Thu, 14 Apr 2005 11:01:01 -0700	[thread overview]
Message-ID: <5fc59ff305041411013fd35ed4@mail.gmail.com> (raw)
In-Reply-To: <42431734.3030905@candelatech.com>

Ben:

Have you checked if the BIOS on the super micro machine is the latest
and greatest. I have had interrupt routing issues very similar to the
one you are describing due to a BIOS Interrupt Routing issue. Moving
to newer BIOS fixed it.

ganesh.

On 3/24/05, Ben Greear <greearb@candelatech.com> wrote:
> Lennert Buytenhek wrote:
> > On Wed, Mar 23, 2005 at 06:03:30PM -0800, Ben Greear wrote:
> >
> >
> >>I have two 4-port e1000 NICs in the system, on a riser card.
> >
> >
> > How is the riser card wired?  F.e. does it have a single edge
> > connector, and provides two PCI slots, or does it have a tiny
> > additional edge connector that routes REQ#/GNT#/INTx from a
> > nearby PCI slot, etc.?
> 
> I was able to reproduce the problem even when the 4-port e1000 NIC
> is plugged directly into the motherboard, so it's not the
> riser...
> 
> I also tried with a 4-port VIA-Rhine NIC (router-board 44).  It also
> fails it's third interface, with the same problem.  So, it is not
> the e1000 NIC nor the e1000 driver that is the problem.
> 
> I do notice that it is the same interrupt (26) that is always assigned
> to the broken port.  I have the lspci and dmesg output for the via-rhine
> boot if anyone wants it...
> 
> Ben
> 
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 
>

  parent reply	other threads:[~2005-04-14 18:01 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
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     ` Ganesh Venkatesan [this message]
2005-04-14 20:34       ` PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard 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=5fc59ff305041411013fd35ed4@mail.gmail.com \
    --to=ganesh.venkatesan@gmail.com \
    --cc=buytenh@wantstofly.org \
    --cc=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).