From: Ben Greear <greearb@candelatech.com>
To: Ganesh Venkatesan <ganesh.venkatesan@gmail.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 13:34:17 -0700 [thread overview]
Message-ID: <425ED3C9.5090600@candelatech.com> (raw)
In-Reply-To: <5fc59ff305041411013fd35ed4@mail.gmail.com>
Ganesh Venkatesan wrote:
>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.
>
>
A new BIOS didn't help. Super-Micro eventually reproduced the problem,
and told me
the fix was to send the MB back to them so they could solder another part
onto it.... I haven't received the MB back yet so I don't know if they
really
have a fix for it or not...
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-04-14 20:34 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 ` PCI interrupt problem: e1000 & Super-Micro X6DVA motherboard Ganesh Venkatesan
2005-04-14 20:34 ` Ben Greear [this message]
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=425ED3C9.5090600@candelatech.com \
--to=greearb@candelatech.com \
--cc=buytenh@wantstofly.org \
--cc=ganesh.venkatesan@gmail.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).