From: Ananda Sathyanarayana <ananda@versa-networks.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] i354 autoneg-off link issue
Date: Sun, 11 Feb 2018 01:17:09 +0000 [thread overview]
Message-ID: <BY2PR1101MB11269E552BEF07A3942A7671E3F00@BY2PR1101MB1126.namprd11.prod.outlook.com> (raw)
Hi,
I am observing a strange issue with i354 when auto-negotiation is turned off. The device I have has 6 ethernet ports. Port 1 and 2 are based on i210 and port 3 to 6 are based on i354 (connected thru an external PHY). The CPU is Atom Rangeley (4 core).
I have connected ports 3 and 4 back to back with an external cable. When the link is forced to 100M/Full duplex with auto-negotiation off on both the ports, the link does not come up.
Whereas the link comes up fine when eth3 (i354) and eth1 (i210) are connected back to back and forced to 100M/Full duplex with auto-negotiation off.
This issue is seen with DPDK (16.04) and also linux kernel (ubuntu 14.04).
Is this a known issue ?
Following are logs when running the test using ethtool from linux
admin@Ananda-Desk:~$ lspci | grep Ethernet
00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 03) - eth2
00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 03) - eth3
00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 03) - eth4
00:14.3 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 03) - eth5
01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) - eth0
02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) - eth1
admin@Ananda-Desk:~$ ethtool -i eth3
driver: igb
version: 5.2.13-k
firmware-version: 0.0.0
bus-info: 0000:00:14.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
[Force 100M/Full on eth3]
admin@Ananda-Desk:~$ sudo ethtool -s eth3 autoneg off duplex full speed 100
admin@Ananda-Desk:~$ ethtool eth3
Settings for eth3:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
admin@Ananda-Desk:~$ ethtool eth4
Settings for eth4:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
[Force 100M/Full on eth4]
admin@Ananda-Desk:~$ sudo ethtool -s eth4 autoneg off duplex full speed 100
admin@Ananda-Desk:~$
admin@Ananda-Desk:~$ ethtool eth4
Settings for eth4:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: off
MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: no <<<<<<<<<<<<<<
admin@Ananda-Desk:~$ ethtool eth3
Settings for eth3:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: no <<<<<<<<<<<
[Connect cables between eth1 and eth3]
[Force 100M/Full on eth1]
admin@Ananda-Desk:~$
admin@Ananda-Desk:~$ sudo ethtool -s eth1 autoneg off duplex full speed 100
admin@Ananda-Desk:~$
admin@Ananda-Desk:~$ ethtool eth1
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes <<<<<<<<<<<<
admin@Ananda-Desk:~$ ethtool eth3
Settings for eth3:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: off
MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes <<<<<<<<<<<<
Thanks,
Ananda
reply other threads:[~2018-02-11 1:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BY2PR1101MB11269E552BEF07A3942A7671E3F00@BY2PR1101MB1126.namprd11.prod.outlook.com \
--to=ananda@versa-networks.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).