From: Ben Greear <greearb@candelatech.com>
To: sfeldma@pobox.com
Cc: Jos Vos <jos@xos.nl>, netdev@oss.sgi.com
Subject: Re: e1000 driver problem with Intel Pro/1000 MT adapter
Date: Sun, 05 Dec 2004 00:37:19 -0800 [thread overview]
Message-ID: <41B2C8BF.9050204@candelatech.com> (raw)
In-Reply-To: <1102204801.3343.68.camel@sfeldma-mobl.dsl-verizon.net>
Scott Feldman wrote:
> On Fri, 2004-12-03 at 15:25, Jos Vos wrote:
>
>>I have a problem with an Intel Pro/1000 MT 4-port card in a Supermicro
>>(non-HT) Pentium 4 system using RHEL3 (2.4.21 kernel "the RH way") with
>>the e1000 driver (I tried both the version supplied by RH and the
>>newest 5.5.4 driver):
>
>
> The 4-port card has two 82546 dual-port controllers behind a PCI-X
> bridge. Your symptoms suggest interrupt routing didn't get setup
> correctly for the controllers behind the bridge. I've seen more than
> one case where the BIOS gets this wrong. The fix is to upgrade to the
> latest BIOS. Hopefully this is the fix for you. :-)
For what it's worth, I've had good luck with a 4-port pro/1000 NIC
in a SuperMicro X5-DPAGG (dual xeon, PCI-X) motherboard. I've tried it with kernel
2.4.27 and 2.6.9 so far... For maximum performance, I needed to increase
the tx and rx descriptors to 2k, I believe this helps mitigate the extra
latency caused by the PCI-X bridge on the NIC...
Ben
>
> -scott
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2004-12-05 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 23:25 e1000 driver problem with Intel Pro/1000 MT adapter Jos Vos
2004-12-04 0:59 ` Francois Romieu
2004-12-04 1:14 ` Jos Vos
2004-12-04 12:03 ` Francois Romieu
2004-12-04 17:20 ` Jos Vos
2004-12-05 0:00 ` Scott Feldman
2004-12-05 8:37 ` Ben Greear [this message]
2004-12-06 9:42 ` Jos Vos
2004-12-06 11:51 ` Jos Vos
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=41B2C8BF.9050204@candelatech.com \
--to=greearb@candelatech.com \
--cc=jos@xos.nl \
--cc=netdev@oss.sgi.com \
--cc=sfeldma@pobox.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).