** Tags added: canonical-bootstack
--
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.10 (or
4.8.0-49, xenial-hwe)
To
Re-open zesty task because some patches are still missing (for example
the fix for openvswitch).
** Changed in: linux (Ubuntu Yakkety)
Assignee: Joseph Salisbury (jsalisbury) => Jesse Sung (wenchien)
** Changed in: linux (Ubuntu Zesty)
Status: Fix Released => In Progress
** Changed
@Thiago, same for us. Hope it will be fixed soon !
--
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.10 (or
4.8.0-49,
I'm also expecting this on Xenial ASAP!
I'm using OpenStack with OVN, and the OpenFlow rules does not work with
Kernel 4.4! And MTU does not work with 4.8!
Very bad situation... :-(
Also expecting the fix for:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742
...in one
Any chance, that xenial will be fixed anytime soon? :-)
--
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.10 (or
4.8.0-49,
Nice goldyfruit, thank you!
--
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.10 (or
4.8.0-49, xenial-hwe)
To manage
@Thiago, yes I confirm.
--
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.10 (or
4.8.0-49, xenial-hwe)
To manage
@goldyfruit, can you confirm if it also fixes the BUG:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742 ?
Thanks!
--
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:
Downgraded to 4.4 series. :(
--
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.10 (or
4.8.0-49, xenial-hwe)
To manage
@martinx - To mitigate the problem I've dropped temporally jumbo frames
from the configuration of my servers.
Hopefully the bug will be fixed also for xenial-hwe and not only for
yakkety ;-)
I agree that this is a *blocker* for xenial.
--
You received this bug notification because you are a
** Summary changed:
- bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
+ bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49,
xenial-hwe)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The kernel in #38 does fix this for Zerotier TAP interfaces as 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
Title:
bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
I also have a production environment running into network issues...
Planning to downgrade the kernel to 4.4 series...=(
--
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:
Sorry, I can't do experiments on production server :-(
I was hoping that on stable LTS release they would avoid doing
experiments to avoid such... bummers :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@michal did you try this kernel:
https://people.canonical.com/~jesse/lp1679823v2/ ?
--
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
mlx4_en ( Mellanox Technologies MT26448 )
4.8.0-49-generic
->
enp3s0: Invalid MTU 9000 requested, hw max 68
--
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
Success.
#38 works with ixgbe
@Jesse thanks and good job !
--
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.10 (or
Success.
#38 works with bnx2x
Thanks a lot.
--
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.10 (or
4.8.0-49)
To manage
Hi @narurien and @gaetan-trellu,
Please try
https://people.canonical.com/~jesse/lp1679823v2/
--
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
Hi Jesse,
Same behavior for me as @Henning.
Kernel:
ii linux-image-4.8.0-52-generic4.8.0-52.55~16.04.1
Error:
kernel: [ 53.900687] ha-4fbfe106-23: Invalid MTU 8950 requested, hw max 1500
ixgbe NIC driver.
--
You received this bug notification because you are a member of Ubuntu
Another commit is required for bnx2x, let me build a test kernel with
it.
--
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
Unfortunately still failing for me with kernel from #34
Summary of testing on Xenial (bnx2x NIC driver):
4.8.0-46: all OK
4.8.0-49: all interfaces fail with "hw max 68"
4.10.0-20: physical interfaces work, openvswitch bridges fail with "hw max 1500"
4.8.0-52: all interfaces fail with "hw max
@jsalisbury: I figured it out...
We're talking about two issues here.
The first one is unable to set MTU larger than 1500 on some devices.
Commit e84f31d (yakkety), "net: centralize net_device min/max MTU
checking", introduced net_device.min_mtu and net_device.max_mtu. These
values will be
Thanks, Jesse. I'll investigate further. I'll probably try to
reproduce the bug to make debugging faster.
--
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
It still fails with the kernel in #31.
$ uname -a
Linux cola 4.8.0-49-generic #52~lp1679823v2 SMP Mon May 1 21:32:12 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep enp4s0
[1.197150] e1000e :04:00.0 enp4s0: renamed from eth0
[ 52.924244] enp4s0: Invalid MTU 9000 requested, hw
After a review, Yakkety did get the following commits via other bug
reports:
d37117d ethernet: use net core MTU range checking in more drivers
6426a88 net: use core MTU range checking in virt drivers
89110d9 net: use core MTU range checking in virt drivers
e84f31d net: centralize net_device
It appears commit 3331aa378e9 fixes commit 91572088e3fd. However,
commit 91572088e3fd was introduced in v4.10-rc1 and not cc'd to stable.
The Yakkety 4.8 kernel never had commit 91572088e3fd applied. That
explains why my test kernel did not fix this bug.
Comment #6 says that this same issue
Thanks for the testing feedback on my test kernel. I suspect more than
just commit 3331aa378e9bcbd0d16de9034b0c20f4050e26b4 is needed.
dev->max_mtu being set to ETH_MAX_MTU must be needed in other spots.
I'll investigate and post another test kernel shortly.
--
You received this bug
any news about kernel 4.10.0-20 to fix also openvswitch interfaces (bug
1685742) ?
--
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
@jsalisbury: I can still reproduce this issue with the kernel in #12...
$ uname -a
Linux cola 4.8.0-49-generic #52~lp1679823 SMP Tue Apr 25 17:29:26 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg | grep enp4s0
[1.194350] e1000e :04:00.0 enp4s0: renamed from eth0
[ 53.469795] enp4s0:
Can folks affected by this bug see if it is fixed with the kernel posted
in comment #12? To test that kernel you would need to install both the
linux-image and linux-image-extra .deb packages. You should see this
bug number in the output of uname -a if it the kernel is installed and
booted.
--
I was experiencing issues with OpenStack deployed with Networking OVN
and just saw this message in my dmesg:
---
[ 12.241706] 8021q: adding VLAN 0 to HW filter on device eno2
[ 15.077293] eno2: Invalid MTU 9000 requested, hw max 68
---
And the IP of my eno2.600 VLAN is gone! So, the
Any progress in fixing this issue for xenial hwe 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 with kernel 4.10 (or
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe (Ubuntu Zesty)
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe (Ubuntu Yakkety)
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-edge (Ubuntu Yakkety)
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-hwe-edge (Ubuntu Zesty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It affects Neutron, qr-* and ha-* interfaces can be set with a MTU higher than
1500.
Look the output in #13 comment.
--
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
** No longer affects: neutron
--
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.10 (or
4.8.0-49)
To manage notifications
@jsalisbury: The systems here running xenial with hwe kernel.
T
--
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.10 (or
1. xenial is missing in linux-hwe distributions
2. @jsalisbury: The systems here running xenial with hwe 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
@Joseph, I tried with 4.10.0-20-generic
--
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.10 (or
4.8.0-49)
To manage
@goldyfruit, your still having an issue with the test kernel I posted in
comment #12?
--
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
Still having and issue, for the physical interface it's working as
expected but for virtual interfaces I got the same error.
I'm trying to change MTU on an OpenVswitch interface in a kernel
namespace. If I switch back to 4.8.0-46 everything is OK.
Apr 25 19:44:11 controller003 kernel: [
I built a Yakkety test kernel with a pick of commit
3331aa378e9bcbd0d16de9034b0c20f4050e26b4. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1679823/
Can folks affected by this bug give this kernel a test?
Thanks in advance!
--
You received this bug
@Joseph, 4.10.0-20-generic works for me.
Thanks !
--
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.10 (or
4.8.0-49)
To
The fix to this bug is in the Ubuntu-4.10.0-15.17 kernel.
I'll build a 4.8 test kernel with the patch and post a link to it
shortly.
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux-hwe-edge (Ubuntu Zesty)
Importance: Undecided
The automatic generated url leads to a 404
** Bug watch added: Linux Kernel Bug Tracker #194763
http://bugzilla.kernel.org/194763
--
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:
48 matches
Mail list logo
