Mlx5 EN - Ethtool link speed setting fixes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Wily |
Fix Released
|
Undecided
|
Tim Gardner | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Setting link speed for ConnectX4 is not working.
reproduce
ethtool -s ens1 speed 10000
ethtool -s ens1 |grep Speed
Speed: 40000
The commit below fix this issue is
commit 6fa1bcab6be6e9b
Author: Achiad Shochat <email address hidden>
Date: Sun Aug 16 16:04:50 2015 +0300
net/mlx5e: Ethtool link speed setting fixes
- Port speed settings are applied by the device only upon
port admin status transition from DOWN to UP.
So we enforce this transition regardless of the port's
current operation state (which may be occasionally DOWN if
for example the network cable is disconnected).
- Fix the PORT_UP/DOWN device interface enum
- Set the local_port bit in the device PAOS register
- EXPORT the PAOS (Port Administrative and Operational Status)
register set/query access functions.
Signed-off-by: Achiad Shochat <email address hidden>
Signed-off-by: David S. Miller <email address hidden>
I cherry -pick it to Ubuntu 15.10 (please see the attached patch) and test it.
could you please add the fix also in Ubuntu 14.04.4 not only 15.10.
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily
# uname -a
Linux dev-h-vrt-006 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Changed in linux (Ubuntu Xenial): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Wily): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | New → In Progress |
Changed in linux (Ubuntu Wily): | |
status: | In Progress → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1517919
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.