bonding - mlx5 - speed changed to 0 after changing ring size
Bug #1687877 reported by
Talat Batheesh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
meenmeng | ||
Xenial |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The problem happens when changing the ring size of a mlx5_core interface that is part of a LACP bond.
[268312.721076] mlx5_core 0000:42:00.1 enp66s0f1: mlx5e_update_
[268312.721940] mlx5_core 0000:42:00.1 enp66s0f1: speed changed to 0 for port enp66s0f1
[268312.732089] bond0: link status up again after 0 ms for interface enp66s0f1
the upstream commit "bonding: allow notifications for bond_set_
Thanks,
Talat
CVE References
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
status: | New → In Progress |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
tags: | added: xenial |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
Changed in linux (Ubuntu): | |
assignee: | nobody → meenmeng (meenmeng) |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1687877
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.