Hi Akeem,
I have tested the same scenario with below driver version
# ethtool -i front_eth1
driver: igb
version: 3.1.16
and the issue is reolved in the above driver.From sourceforge i got below
change log for igb-3.1.16
*Changelog for igb-3.1.16
========================*
** Fix for Malicious Driver Detection Feature on i350 devices in a
virutalized environment.
* Add module parameter for DMA Coalescing feature to allow user to
determine approximate latency setting at init.
* Updated DMA Coalescing init parameters per performance test lab results.
Feature now saves more power.
* Fix for problem found in pre-release RHEL 5.7 which caused a panic at
device configuration.
* Added function to set rx_hash and a call to it during receive. Not
changeable by ethtool at this time, however.*
Any idea what code changes have been added to fix this issue.
Thanks
Abhinay
---------- Forwarded message ----------
From: Abodunrin, Akeem G <[email protected]>
Date: Mon, Dec 17, 2012 at 6:46 PM
Subject: RE: [E1000-devel] Information needed regarding igb driver
To: abhinay aruva <[email protected]>, "Kirsher, Jeffrey T" <
[email protected]>
Cc: "Wyborny, Carolyn" <[email protected]>, e1000-devel <
[email protected]>, "Brandeburg, Jesse" <
[email protected]>, "[email protected]" <[email protected]>
Hi Abhinay,****
** **
I’m having difficulty to reproduce this issue here. Please send me "lspci
-vvv" log and ethregs dump, so that I could establish information about
Intel devices you are using and other *runtime* configurations.****
** **
Also, tell me about Linux OS and Kernel that you are using. ****
** **
In addition, we have latest igb-driver (igb-4.0.17) recently posted on
SourceForge. Please try it as well… ****
** **
Regards,****
** **
~Akeem****
** **
*From:* abhinay aruva [mailto:[email protected]]
*Sent:* Monday, December 17, 2012 3:13 AM
*To:* Abodunrin, Akeem G; Kirsher, Jeffrey T
*Cc:* Wyborny, Carolyn; e1000-devel; Brandeburg, Jesse; [email protected]
*Subject:* Re: [E1000-devel] Information needed regarding igb driver****
** **
Hi All,****
****
Please consider this as a gentle reminder and can you let me know if you
know any information regarding this issue.****
****
Thanks****
Abhinay****
****
On Thu, Dec 13, 2012 at 1:50 PM, abhinay aruva <[email protected]>
wrote:****
---------- Forwarded message ----------
From: *abhinay aruva* <[email protected]>
Date: Thu, Dec 13, 2012 at 12:06 PM
Subject: Re: [E1000-devel] Information needed regarding igb driver****
To: "Abodunrin, Akeem G" <[email protected]>, "Kirsher, Jeffrey
T" <[email protected]>
Cc: "Wyborny, Carolyn" <[email protected]>, e1000-devel <
[email protected]>, "Brandeburg, Jesse" <
[email protected]>, "[email protected]" <[email protected]>
****
Hi All,****
****
Thanks for your replies. Sorry for late reply. I couldnot get the hardware
to test this scenario again and i was also busy with some other things.****
****
@Akeem: It is back to back connection, there is no switch in between. We
didnt try on the latest igb-driver.****
****
@Jeff: Please find the output of the ethtool command executed after one
interface is made admin down.****
****
*Output of ethtool command on ATCA on which the interface is made down*****
* *****
*# ethtool front_eth1**
Settings for front_eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: no*****
****
*Output of ethtool command on remote ATCA*****
****
*# ethtool front_eth1**
Settings for front_eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: umbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
* ****
Can you please check and let us know your opinion. Feel free to reply back
if you need further information.****
****
Thanks****
Abhinay****
On Tue, Dec 4, 2012 at 7:36 PM, Abodunrin, Akeem G <
[email protected]> wrote:****
Hi Abhinay,
Is this back-to-back connection or through a switch?
Also, did you try latest igb-driver on SourceForge?
Regards,
~Akeem****
-----Original Message-----
From: Jeff Kirsher [mailto:[email protected]]
Sent: Tuesday, December 04, 2012 3:51 AM
To: abhinay aruva; Wyborny, Carolyn
Cc: e1000-devel; Brandeburg, Jesse; [email protected]
Subject: Re: [E1000-devel] Information needed regarding igb driver
On Sun, 2012-12-02 at 09:39 +0530, abhinay aruva wrote:
> Hi All,
>
> I am working on developing software for a networking company. We are
> facing issue with igb driver code implemented on our ethernet
> interface
>
> We have connected two ethernet interfaces which are on two different
> ATCA machines as mentioned.
>
> ATCA1:front_eth1 ----------> ATCA2:front_eth1
>
> Both the ethernet interfaces use igb drivers.The version of these
> drivers when checked with ethtool command is below
>
> ethtool -i front_eth1
> driver: igb
> version: 2.0.6-fpn
> firmware-version: 2.1-1
> bus-info: 0000:04:00.1
>
> We are testing below scenario:
> We are pinging one interface from the other one and the ping is
> working fine when both the interfaces admin and operational state are
> UP . Now we have made the the 'front_eth1' interface on ATCA2 admin
> down using 'iplink set front_eth1 down'.Then the ping stoped working
> and 'front-eth1' interface admin state and operational state on ATCA2
> are now down where as the 'front_eth1' interface admin status and
> operational status on the ATCA1 are still are up. Accoring to our
> knowledge the 'front_eth1' interface operational status on ATCA1
> should go down when the remote peers interface is made down.
>
> Can you please let us know wether this is an issue or is it the valid
> behaviour on the igb driver. If this is an issue can you please give
> us some pointers where to check to find the root cause of this
> problem.
>
> Thanks
> Abhinay
Abhinay-
I have added Carolyn, since she is the igb maintainer. I have also added
the e1000-devel mailing list to open up this to a wider audience.
After taking down one of the interfaces, what is ethtool reporting for link
both interfaces? (ethtool eth1)
Cheers,
Jeff****
** **
** **
** **
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
