Mellanox ConnectX4 MTU limits: max and min
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Wily |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
linux-lts-wily (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Max MTU limit should be 9978
Tested on Ubuntu 14.04.4 daily build, this issue exist also in 15.10.
reproduce
# ifconfig p2p1 mtu 9000000
SIOCSIFMTU: Invalid argument
# dmesg
[62898.559808] mlx5_core 0000:20:00.0 p2p1: mlx5e_change_mtu: Bad MTU (9000000) > (10000) Max
[63058.512668] command failed, status bad parameter(0x3), syndrome 0x648afc
Upstream commit that fix the issue
commit 60825c35bf02355
Author: Doron Tsur <email address hidden>
Date: Thu Nov 12 19:35:27 2015 +0200
net/mlx5e: Max mtu comparison fix
On change mtu the driver compares between hardware queried mtu and
software requested mtu. We need to compare between software
representation of the queried mtu and the requested mtu.
Fixes: facc9699f0fe ('net/mlx5e: Fix HW MTU settings')
Signed-off-by: Doron Tsur <email address hidden>
Signed-off-by: Saeed Mahameed <email address hidden>
Signed-off-by: Or Gerlitz <email address hidden>
Signed-off-by: David S. Miller <email address hidden>
# cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04.3 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.3 LTS"
VERSION_ID="14.04"
HOME_URL="http://
SUPPORT_URL="http://
BUG_REPORT_URL="http://
# uname -r
4.2.0-22-generic
tags: | added: trusty |
tags: | added: vivid wily |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu Vivid): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Wily): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in linux-lts-vivid (Ubuntu): | |
status: | New → Triaged |
Changed in linux-lts-vivid (Ubuntu Vivid): | |
status: | New → Triaged |
Changed in linux-lts-vivid (Ubuntu Wily): | |
status: | New → Triaged |
Changed in linux-lts-wily (Ubuntu): | |
status: | New → Triaged |
Changed in linux-lts-wily (Ubuntu Vivid): | |
status: | New → Triaged |
Changed in linux-lts-wily (Ubuntu Wily): | |
status: | New → Triaged |
Changed in linux-lts-vivid (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux-lts-vivid (Ubuntu Vivid): | |
importance: | Undecided → Medium |
Changed in linux-lts-wily (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux-lts-wily (Ubuntu Vivid): | |
importance: | Undecided → Medium |
Changed in linux-lts-wily (Ubuntu Wily): | |
importance: | Undecided → Medium |
no longer affects: | linux-lts-wily (Ubuntu Vivid) |
no longer affects: | linux-lts-wily (Ubuntu Wily) |
no longer affects: | linux-lts-vivid (Ubuntu Wily) |
no longer affects: | linux-lts-vivid (Ubuntu Vivid) |
Changed in linux (Ubuntu Wily): | |
status: | Triaged → In Progress |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux-lts-wily (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux-lts-vivid (Ubuntu): | |
status: | Triaged → Incomplete |
Changed in linux (Ubuntu Vivid): | |
status: | Triaged → Incomplete |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
no longer affects: | linux-lts-vivid (Ubuntu) |
no longer affects: | linux (Ubuntu Vivid) |
tags: | removed: trusty vivid |
Changed in linux (Ubuntu Wily): | |
status: | In Progress → Fix Committed |
tags: | added: verification-done-wily |
Changed in linux (Ubuntu Xenial): | |
status: | New → Fix Committed |
no longer affects: | linux-lts-wily (Ubuntu Xenial) |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1528466
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.