RE: [E1000-devel] 2.6.39: kernel igb and e1000e-1.3.17 driver broken?

["Wyborny, Carolyn" <carolyn.wyborny@intel.com>]

>-----Original Message-----
>From: Justin Piszcz [mailto:jpiszcz@lucidpixels.com]
>Sent: Wednesday, May 25, 2011 4:43 PM
>To: linux-kernel@vger.kernel.org
>Cc: e1000-devel@lists.sourceforge.net; linux-net@vger.kernel.org
>Subject: Re: [E1000-devel] 2.6.39: kernel igb and e1000e-1.3.17 driver
>broken?
>
>
>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.
>
>
>------------------------------------------------------------------------
>------
>vRanger cuts backup time in half-while increasing security.
>With the market-leading solution for virtual backup and recovery,
>you get blazing-fast, flexible, and affordable data protection.
>Download your free trial now.
>http://p.sf.net/sfu/quest-d2dcopy1
>_______________________________________________
>E1000-devel mailing list
>E1000-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/e1000-devel
>To learn more about Intel&#174; Ethernet, visit
>http://communities.intel.com/community/wired

No problem Justin, let us know if you still find a problem.

Thanks,

Carolyn

Carolyn Wyborny
Linux Development
LAN Access Division
Intel Corporation