RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1895393 - ethtool: not all supported link modes are advertised when only autoneg on is specified
Summary: ethtool: not all supported link modes are advertised when only autoneg on is ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ethtool
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.4
Assignee: Ivan Vecera
QA Contact: Tianhao
URL:
Whiteboard:
Depends On: 1878826
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-06 14:54 UTC by Ivan Vecera
Modified: 2021-05-18 13:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 13:35:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ivan Vecera 2020-11-06 14:54:06 UTC 
Description of problem:
With older ethtool version (<5.8) that is based on ioctl interface the advertised link modes are set to the supported link modes when only autoneg on is set without specifying speed, duplex or link modes.
This is not true for newer ethtool (>=v5.8) that just enable auto-negotiation but leaves advertised link modes untouched.

Version-Release number of selected component (if applicable):
ethtool-5.8-3.el8

How reproducible:
100% with mlxsw driver

Steps to Reproduce:
1. Enable auto-negotiation but limit advertised link modes
2. Check link status
3. Enable auto-negotiation (no limitation)
4. Check link status

Actual results:

1. Enable autoneg and limit advertised link modes to 10Gbit
[root@mlxsw-1 ~]# ethtool -s enp6s0np17 autoneg on speed 10000

2. Verify
[root@mlxsw-1 ~]# ethtool enp6s0np17
Settings for enp6s0np17:
...
        Advertised link modes:  10000baseT/Full
                                10000baseKR/Full
                                10000baseR_FEC
                                10000baseCR/Full
                                10000baseSR/Full
                                10000baseLR/Full
                                10000baseER/Full
...

3. Enable autoneg without any limit
[root@mlxsw-1 ~]# ethtool -s enp6s0np17 autoneg on

4. Verify:
[root@mlxsw-1 ~]# ethtool enp6s0np17
Settings for enp6s0np17:
...
        Advertised link modes:  10000baseT/Full
                                10000baseKR/Full
                                10000baseR_FEC
                                10000baseCR/Full
                                10000baseSR/Full
                                10000baseLR/Full
                                10000baseER/Full
...
Advertised link-modes are still limited ^^^^^^^^


Expected results:
1. Enable autoneg and limit advertised link modes to 10Gbit
[root@mlxsw-1 ~]# ethtool -s enp6s0np17 autoneg on speed 10000

2. Verify
[root@mlxsw-1 ~]# ethtool enp6s0np17
Settings for enp6s0np17:
...
        Advertised link modes:  10000baseT/Full
                                10000baseKR/Full
                                10000baseR_FEC
                                10000baseCR/Full
                                10000baseSR/Full
                                10000baseLR/Full
                                10000baseER/Full
...

3. Enable autoneg without any limit
[root@mlxsw-1 ~]# ethtool -s enp6s0np17 autoneg on

4. Verify:
[root@mlxsw-1 ~]# ethtool enp6s0np17
Settings for enp6s0np17:
...
        Advertised link modes:  1000baseT/Full
                                10000baseT/Full
                                1000baseKX/Full
                                10000baseKR/Full
                                10000baseR_FEC
                                40000baseKR4/Full
                                40000baseCR4/Full
                                40000baseSR4/Full
                                40000baseLR4/Full
                                25000baseCR/Full
                                25000baseKR/Full
                                25000baseSR/Full
                                50000baseCR2/Full
                                50000baseKR2/Full
                                100000baseKR4/Full
                                100000baseSR4/Full
                                100000baseCR4/Full
                                100000baseLR4_ER4/Full
                                50000baseSR2/Full
                                10000baseCR/Full
                                10000baseSR/Full
                                10000baseLR/Full
                                10000baseER/Full
...

All possible link modes are reported ^^^^^^^
Comment 5 Tianhao 2020-11-26 06:40:50 UTC 
Hi Ivan,

Could you also prepare the test HW for me as in comment #1 to verify the bug?

Thanks in advance.
Regards,
Tianhao
Comment 8 Tianhao 2020-11-27 01:35:32 UTC 
Set verified based on comment #6 and comment #7.
Comment 10 errata-xmlrpc 2021-05-18 13:35:02 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (ethtool bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1576
Note You need to log in before you can comment on or make changes to this bug.