> I have the same problem with my DELL server. Can't set MTU > 1500 with
current kernel.
Your hardware is limited, you are not seeing a kernel bug. Your tg3
chip has a "jumbo capable" flag and it seems it not set - meaning your
NIC does not support frames larger than the standard 1500.
/*
I have the same problem with my DELL server. Can't set MTU > 1500 with
current kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid MTU 9000 requested, hw max 1500
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Feb 16 13:45 seq
crw-rw 1 root audio 116, 33 Feb 16 13:45 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
It happens when test for kernel in -proposed (in this case 4.10.0-23) is
not yet completed, and an important security issue must be addressed. In
this case 4.10.0-24 is based on a fully tested 4.10.0-22, and changes in
4.10.0-23 will be included in later release instead.
--
You received this bug
# apt update
[...]
# apt install linux-image-4.10.0-23-generic
N: Unable to locate package linux-image-4.10.0-23-generic
(yes I know it is in proposed)
However, 4.10.0-24 does exist and gets installed with -edge. And it is
known broken. Why push it out at all? Am I wrong to assume that a later
4.10.0-24 is a 4.10.0-22 with CVE fix applied, that's why it doesn't
have the fix for openvswitch which is in 4.10.0-23.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid
The MTU problem affecting OpenvSwitch bridges still exists (or
resurfaced) in linux-generic-hwe-16.04-edge (4.10.0.24.17).
# grep -i mtu /var/log/syslog
[...] br-int: Invalid MTU 9000 requested, hw max 1500
[...] lxcbr0: Invalid MTU 9000 requested, hw max 1500
Pretty please STOP BREAKING things.
linux-generic-hwe-16.04-edge from xenial-proposed repo fixes the
problem.
$ sudo cat /etc/apt/sources.list | grep proposed
deb http://archive.ubuntu.com/ubuntu xenial-proposed main
$ sudo apt-cache policy linux-generic-hwe-16.04-edge
linux-generic-hwe-16.04-edge:
Installed: 4.10.0.23.16
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-edge (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
@shapemaker:
Since it's "fix committed" for lp:1691369, the fix will be included in
the next SRU release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid MTU 9000
Ok, so the fix is rather trivial. I've verified that building 4.10.0-22
kernel from Ubuntu sources with the following patch fixes the
OpenvSwitch MTU issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/openvswitch
4.10 series (hwe-edge) kernel doesn't seem to have gotten these fixes
yet, as 4.10.0-22-generic #24~16.04.1-Ubuntu still fails to set
openvswitch MTU correctly. When can we expect a fix to be released for
-edge?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@vaaend:
@smb pointed out that it is part of the stable 4.10.16:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691369
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0:
Any progress on Zesty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
in XENIAL LTS
To manage notifications
This bug was fixed in the package linux-hwe - 4.8.0-54.57~16.04.1
---
linux-hwe (4.8.0-54.57~16.04.1) xenial; urgency=low
* linux-hwe: 4.8.0-54.57~16.04.1 -proposed tracker (LP: #1692590)
* linux: 4.8.0-54.57 -proposed tracker (LP: #1692589)
* CVE-2017-0605
- tracing: Use
This bug was fixed in the package linux-hwe - 4.8.0-54.57~16.04.1
---
linux-hwe (4.8.0-54.57~16.04.1) xenial; urgency=low
* linux-hwe: 4.8.0-54.57~16.04.1 -proposed tracker (LP: #1692590)
* linux: 4.8.0-54.57 -proposed tracker (LP: #1692589)
* CVE-2017-0605
- tracing: Use
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-hwe-edge (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-hwe (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug
This bug was fixed in the package linux-hwe - 4.8.0-53.56~16.04.1
---
linux-hwe (4.8.0-53.56~16.04.1) xenial; urgency=low
* linux-hwe: 4.8.0-53.56~16.04.1 -proposed tracker (LP: #1690957)
* linux: 4.8.0-53.56 -proposed tracker (LP: #1690956)
* bond0: Invalid MTU 9000
This bug was fixed in the package linux - 4.8.0-53.56
---
linux (4.8.0-53.56) yakkety; urgency=low
* linux: 4.8.0-53.56 -proposed tracker (LP: #1690956)
* bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in
XENIAL LTS (LP: #1679823)
- Revert
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid MTU 9000 requested, hw max 1500
So for me the situation with 4.8.0-53 is that in contradiction to 4.8.0-49 the
system is working again and doesn't suffer from broken network configuration.
So it isn't a blocker any more.
But there is a conflict with the bond0 configuration on my systems now.
--
You received this bug
Linux odie 4.8.0-53-generic #56~16.04.1-Ubuntu SMP Tue May 16 01:18:56
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Here the answer is yes and no.
The mtu is configured via systemd-networkd:
# grep MTU /etc/systemd/network/*
/etc/systemd/network/10-c42-bond0.netdev:MTUBytes=9000
Works inside a virtual machine
Linux vt-xenial-server 4.8.0-53-generic #56~16.04.1-Ubuntu SMP Tue May 16
01:14:44 UTC 2017 i686 i686 i686 GNU/Linux
ifconfig lan1
…
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
--
You received this bug notification because you are a member of
With 4.8.0-53 in -proposed, e1000e works without any problem.
$ uname -a
Linux cola 4.8.0-53-generic #56-Ubuntu SMP Tue May 16 00:23:44 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
$ ifconfig eth1
...
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
...
--
You received this bug notification
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag
The fixes for this issue are also included on Xenial linux-hwe
4.8.0-53.56~16.04.1 which is currently on -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid MTU
Sorry about the confusion: the commits are tagged with -53 and I
mentioned -52 in the apt output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid MTU 9000 requested, hw
These patches are in 4.8.0-53, which is in -proposed right now. It will
be available in -updates with next SRU release if everything goes well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
I am running Ubuntu 16.04.2 LTS with 4.8.0-52-generic
(#55~16.04.1-Ubuntu) and still have the problem as reported in
[#6](https://bugs.launchpad.net/ubuntu/+source/linux-hwe-
edge/+bug/1679823/comments/6). Everything should be up to date on my
side, linux-generic-hwe-16.04 is of version
Hi,
Guys, it should be there for both the Yakkety kernel and linux-generic-
hwe-16.04:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=7570ffb5145abf4413421c154077bc31abad1264
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
I second question #56. However, Xenial is not present in the list at the
top so maybe it is being overlooked right now? I could not find out how
to add it, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just a question - is there any progress to fix this showstopper in
xenial ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679823
Title:
bond0: Invalid MTU 9000 requested, hw max 1500 with kernel
** Also affects: linux-meta-hwe (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-meta-hwe (Ubuntu)
** No longer affects: linux-meta-hwe (Ubuntu Yakkety)
** No longer affects: linux-meta-hwe (Ubuntu Zesty)
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
** Changed in: linux-hwe (Ubuntu Yakkety)
Status: Confirmed => Fix Committed
** Changed in: linux-hwe-edge (Ubuntu Yakkety)
Status: Confirmed => Fix Committed
--
You received this bug notification
We really need to get xenial added for its HWE kernels:
we have several BootStacks running with them, mainly for
latest needed drivers while keeping LTS (mellanox for
VNFs as an example)- all these are now obviously at
risk on the next reboot.
Note also that recovering from this issue does
** Summary changed:
- bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49,
xenial-hwe)
+ bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in
XENIAL LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
37 matches
Mail list logo
