From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: e1000-devel@lists.sourceforge.net, linux-net@vger.kernel.org
Subject: Re: 2.6.39: kernel igb and e1000e-1.3.17 driver broken?
Date: Wed, 25 May 2011 19:42:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1105251941550.9120@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1105251926070.9120@p34.internal.lan>
On Wed, 25 May 2011, Justin Piszcz wrote:
> Hello,
>
> I recently bought a 4-port Intel NIC (82580)
>
> 03:00.0 Ethernet controller: Intel Corporation 82580 Gigabit Network
> Connection (rev 01)
> 03:00.1 Ethernet controller: Intel Corporation 82580 Gigabit Network
> Connection (rev 01)
> 03:00.2 Ethernet controller: Intel Corporation 82580 Gigabit Network
> Connection (rev 01)
> 03:00.3 Ethernet controller: Intel Corporation 82580 Gigabit Network
> Connection (rev 01)
>
> Model name: Intel I340 Server Adapter
>
> Which uses this driver:
> | | <M> Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support | |
> | | [ ] Direct Cache Access (DCA) Support | |
>
> I have tried with and without the DCA support.
>
> Out of the four ports in the back, only two work, why is this?
>
> [ CARD ]
> 1 2 3 4
> X X
>
> Where X = working.
>
> I've tried the built-in kernel driver from 2.6.39 as well as the latest
> e1000e driver from sf.net (1.3.17), any thoughts?
>
> eth0: negotiated 1000baseT-FD flow-control, link ok <- onboard
> eth1: negotiated 100baseTx-FD, link ok <- middle port 1
> eth2: negotiated 1000baseT-FD flow-control, link ok <- middle port 2
> eth3: no link <- left most port
> (plugged in)
> eth4: no link <- right most port
> (plugged in)
>
> The last two parts of each mac addr:
>
> eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:f9 WORKING
> eth2 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:fa WORKING
> eth3 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:f8 no link
> eth4 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:fb no link
>
> Thoughts?
>
> Justin.
>
Whoa,
Sent this out too early =)
My mistake, configuration error on user end :)
Problem was interfaces were not initialized properly (not UP).
Please disregard, sorry for the noise!
eth1: negotiated 100baseTx-FD, link ok
eth2: negotiated 1000baseT-FD flow-control, link ok
eth3: negotiated 1000baseT-FD flow-control, link ok
eth4: negotiated 1000baseT-FD flow-control, link ok
Justin.
next prev parent reply other threads:[~2011-05-25 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 23:38 Justin Piszcz
2011-05-25 23:42 ` Justin Piszcz [this message]
2011-05-25 23:46 ` [E1000-devel] " Wyborny, Carolyn
2011-05-25 23:49 ` Justin Piszcz
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=alpine.DEB.2.02.1105251941550.9120@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/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
all inboxes | Powered by JetHome®