[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Dan Streetman]

> 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.

/* hardware minimum and maximum for a single frame's data payload */
#define TG3_MIN_MTU ETH_ZLEN
#define TG3_MAX_MTU(tp) \
(tg3_flag(tp, JUMBO_CAPABLE) ? 9000 : 1500)

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Thomas]

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 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Thomas]

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
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=7d50a0ab-30df-4053-8e22-891d5d2a1aa3
InstallationDate: Installed on 2018-02-14 (8 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge T110 II
Package: linux-hwe-edge (not installed)
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=9d3c0aa3-a21f-406e-a1e4-96f5cd2565cc ro splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic  N/A
 linux-firmware 1.157.16
RfKill: Error: [Errno 2] No such file or directory
Tags:  xenial xenial xenial xenial
Uname: Linux 4.13.0-32-generic x86_64
UnreportableReason: Der Bericht gehört zu einem nicht installierten Paket.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: False
dmi.bios.date: 03/13/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.0.5
dmi.board.name: 0W6TWP
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 17
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.5:bd03/13/2012:svnDellInc.:pnPowerEdgeT110II:pvr:rvnDellInc.:rn0W6TWP:rvrA01:cvnDellInc.:ct17:cvr:
dmi.product.name: PowerEdge T110 II
dmi.sys.vendor: Dell Inc.


** Tags added: apport-collected 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 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Jesse Sung]

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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Mikko Tanner]

# 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
numbered (point?) release would have the fixes contained in previous
versions?

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Jesse Sung]

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 MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Mikko Tanner]

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. No network access is especially
annoying to fix remotely. Luckily I tested this before upgrading more
critical systems (as everyone should, of course).

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Amad Ali]

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
  Candidate: 4.10.0.23.16
  Version table:
 *** 4.10.0.23.16 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.10.0.22.15 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages

$  uname -a
Linux  4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 
10:45:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

$ ip link show | grep bond0
bond0:  mtu 9000 qdisc noqueue master 
br-bond0 state UP mode DEFAULT group default qlen 1000   

$ sudo ovs-vsctl list-br | grep br-int
br-int

$ ip link show | grep br-int
32: br-int:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000

$ sudo ip link set br-int mtu 9000
$ ip link show | grep br-int
32: br-int:  mtu 9000 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000

also solves BUG mentioned in LP#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 kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Launchpad Bug Tracker]

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.
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Launchpad Bug Tracker]

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Jesse Sung]

@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 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Mikko Tanner]

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
/vport-internal_dev.c?id=425df17ce3a26d98f76e2b6b0af2acf4aeb0b026

Here's the instructions for people who want the fixed kernel asap:

# apt-get source linux-image-4.10.0-22-generic
# apt-get build-dep linux-image-4.10.0-22-generic

# fakeroot debian/rules binary-headers binary-generic binary-perarch

Install needed DEBs, reboot.

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Mikko Tanner]

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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Jesse Sung]

@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: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Endre Vaade]

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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Launchpad Bug Tracker]

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 strlcpy() instead of strcpy() in __trace_find_cmdline()

  * Populating Hyper-V MSR for Ubuntu 13.10 (LP: #1193172)
- SAUCE: (no-up) hv: Supply vendor ID and package ABI

  * [Hyper-V] Implement Hyper-V PTP Source (LP: #1676635)
- hv: allocate synic pages for all present CPUs
- hv: init percpu_list in hv_synic_alloc()
- Drivers: hv: vmbus: Prevent sending data on a rescinded channel
- hv: switch to cpuhp state machine for synic init/cleanup
- hv: make CPU offlining prevention fine-grained
- Drivers: hv: vmbus: Fix a rescind handling bug
- Drivers: hv: util: kvp: Fix a rescind processing issue
- Drivers: hv: util: Fcopy: Fix a rescind processing issue
- Drivers: hv: util: Backup: Fix a rescind processing issue
- Drivers: hv: vmbus: Move the definition of hv_x64_msr_hypercall_contents
- Drivers: hv: vmbus: Move the definition of generate_guest_id()
- Revert "UBUNTU: SAUCE: (no-up) hv: Supply vendor ID and package ABI"
- Drivers: hv vmbus: Move Hypercall page setup out of common code
- Drivers: hv: vmbus: Move Hypercall invocation code out of common code
- Drivers: hv: vmbus: Consolidate all Hyper-V specific clocksource code
- Drivers: hv: vmbus: Move the extracting of Hypervisor version information
- Drivers: hv: vmbus: Move the crash notification function
- Drivers: hv: vmbus: Move the check for hypercall page setup
- Drivers: hv: vmbus: Move the code to signal end of message
- Drivers: hv: vmbus: Restructure the clockevents code
- Drivers: hv: util: Use hv_get_current_tick() to get current tick
- Drivers: hv: vmbus: Get rid of an unsused variable
- Drivers: hv: vmbus: Define APIs to manipulate the message page
- Drivers: hv: vmbus: Define APIs to manipulate the event page
- Drivers: hv: vmbus: Define APIs to manipulate the synthetic interrupt
  controller
- Drivers: hv: vmbus: Define an API to retrieve virtual processor index
- Drivers: hv: vmbus: Define an APIs to manage interrupt state
- Drivers: hv: vmbus: Cleanup hyperv_vmbus.h
- hv_util: switch to using timespec64
- Drivers: hv: restore hypervcall page cleanup before kexec
- Drivers: hv: restore TSC page cleanup before kexec
- Drivers: hv: balloon: add a fall through comment to hv_memory_notifier()
- Drivers: hv: vmbus: Use all supported IC versions to negotiate
- Drivers: hv: Log the negotiated IC versions.
- Drivers: hv: Fix the bug in generating the guest ID
- hv: export current Hyper-V clocksource
- hv_utils: implement Hyper-V PTP source
- SAUCE: (no-up) hv: Supply vendor ID and package ABI

  * CIFS: Enable encryption for SMB3 (LP: #1670508)
- SMB3: Add mount parameter to allow user to override max credits
- SMB2: Separate Kerberos authentication from SMB2_sess_setup
- SMB2: Separate RawNTLMSSP authentication from SMB2_sess_setup
- SMB3: parsing for new snapshot timestamp mount parm
- cifs: Simplify SMB2 and SMB311 dependencies
- cifs: Only select the required crypto modules
- cifs: Add soft dependencies
- CIFS: Separate SMB2 header structure
- CIFS: Make SendReceive2() takes resp iov
- CIFS: Make send_cancel take rqst as argument
- CIFS: Send RFC1001 length in a separate iov
- CIFS: Separate SMB2 sync header processing
- CIFS: Separate RFC1001 length processing for SMB2 read
- CIFS: Add capability to transform requests before sending
- CIFS: Enable encryption during session setup phase
- CIFS: Encrypt SMB3 requests before sending
- CIFS: Add transform header handling callbacks
- CIFS: Add mid handle callback
- CIFS: Add copy into pages callback for a read operation
- CIFS: Decrypt and process small encrypted packets
- CIFS: Add capability to decrypt big read responses
- CIFS: Allow to switch on encryption with seal mount option
- CIFS: Fix possible use after free in demultiplex thread

  * APST quirk needed for Samsung 512GB NVMe drive (LP: #1678184)
- nvme: Adjust the Samsung APST quirk
- nvme: Quirk APST off on "THNSF5256GPUK TOSHIBA"

 -- Kleber Sacilotto de Souza   Mon, 22 May
2017 18:56:12 +0200

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Launchpad Bug Tracker]

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 strlcpy() instead of strcpy() in __trace_find_cmdline()

  * Populating Hyper-V MSR for Ubuntu 13.10 (LP: #1193172)
- SAUCE: (no-up) hv: Supply vendor ID and package ABI

  * [Hyper-V] Implement Hyper-V PTP Source (LP: #1676635)
- hv: allocate synic pages for all present CPUs
- hv: init percpu_list in hv_synic_alloc()
- Drivers: hv: vmbus: Prevent sending data on a rescinded channel
- hv: switch to cpuhp state machine for synic init/cleanup
- hv: make CPU offlining prevention fine-grained
- Drivers: hv: vmbus: Fix a rescind handling bug
- Drivers: hv: util: kvp: Fix a rescind processing issue
- Drivers: hv: util: Fcopy: Fix a rescind processing issue
- Drivers: hv: util: Backup: Fix a rescind processing issue
- Drivers: hv: vmbus: Move the definition of hv_x64_msr_hypercall_contents
- Drivers: hv: vmbus: Move the definition of generate_guest_id()
- Revert "UBUNTU: SAUCE: (no-up) hv: Supply vendor ID and package ABI"
- Drivers: hv vmbus: Move Hypercall page setup out of common code
- Drivers: hv: vmbus: Move Hypercall invocation code out of common code
- Drivers: hv: vmbus: Consolidate all Hyper-V specific clocksource code
- Drivers: hv: vmbus: Move the extracting of Hypervisor version information
- Drivers: hv: vmbus: Move the crash notification function
- Drivers: hv: vmbus: Move the check for hypercall page setup
- Drivers: hv: vmbus: Move the code to signal end of message
- Drivers: hv: vmbus: Restructure the clockevents code
- Drivers: hv: util: Use hv_get_current_tick() to get current tick
- Drivers: hv: vmbus: Get rid of an unsused variable
- Drivers: hv: vmbus: Define APIs to manipulate the message page
- Drivers: hv: vmbus: Define APIs to manipulate the event page
- Drivers: hv: vmbus: Define APIs to manipulate the synthetic interrupt
  controller
- Drivers: hv: vmbus: Define an API to retrieve virtual processor index
- Drivers: hv: vmbus: Define an APIs to manage interrupt state
- Drivers: hv: vmbus: Cleanup hyperv_vmbus.h
- hv_util: switch to using timespec64
- Drivers: hv: restore hypervcall page cleanup before kexec
- Drivers: hv: restore TSC page cleanup before kexec
- Drivers: hv: balloon: add a fall through comment to hv_memory_notifier()
- Drivers: hv: vmbus: Use all supported IC versions to negotiate
- Drivers: hv: Log the negotiated IC versions.
- Drivers: hv: Fix the bug in generating the guest ID
- hv: export current Hyper-V clocksource
- hv_utils: implement Hyper-V PTP source
- SAUCE: (no-up) hv: Supply vendor ID and package ABI

  * CIFS: Enable encryption for SMB3 (LP: #1670508)
- SMB3: Add mount parameter to allow user to override max credits
- SMB2: Separate Kerberos authentication from SMB2_sess_setup
- SMB2: Separate RawNTLMSSP authentication from SMB2_sess_setup
- SMB3: parsing for new snapshot timestamp mount parm
- cifs: Simplify SMB2 and SMB311 dependencies
- cifs: Only select the required crypto modules
- cifs: Add soft dependencies
- CIFS: Separate SMB2 header structure
- CIFS: Make SendReceive2() takes resp iov
- CIFS: Make send_cancel take rqst as argument
- CIFS: Send RFC1001 length in a separate iov
- CIFS: Separate SMB2 sync header processing
- CIFS: Separate RFC1001 length processing for SMB2 read
- CIFS: Add capability to transform requests before sending
- CIFS: Enable encryption during session setup phase
- CIFS: Encrypt SMB3 requests before sending
- CIFS: Add transform header handling callbacks
- CIFS: Add mid handle callback
- CIFS: Add copy into pages callback for a read operation
- CIFS: Decrypt and process small encrypted packets
- CIFS: Add capability to decrypt big read responses
- CIFS: Allow to switch on encryption with seal mount option
- CIFS: Fix possible use after free in demultiplex thread

  * APST quirk needed for Samsung 512GB NVMe drive (LP: #1678184)
- nvme: Adjust the Samsung APST quirk
- nvme: Quirk APST off on "THNSF5256GPUK TOSHIBA"

 -- Kleber Sacilotto de Souza   Mon, 22 May
2017 18:56:12 +0200

** Changed in: linux-hwe (Ubuntu Xenial)
   Status: New => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-0605

** Changed in: linux-hwe (Ubuntu Xenial)
   Status: New => Fix Released

-- 
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 

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Brad Figg]

** 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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Launchpad Bug Tracker]

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 requested, hw max 1500 with kernel 4.8 / 4.10 in
XENIAL LTS (LP: #1679823)
- Revert "ethernet: use net core MTU range checking in more drivers"
- Revert "Drivers: hv: ring_buffer: count on wrap around mappings in
  get_next_pkt_raw() (v2)"
- Revert "hyperv: Fix spelling of HV_UNKOWN"
- Revert "uio-hv-generic: new userspace i/o driver for VMBus"
- Revert "UBUNTU: [Config] CONFIG_UIO_HV_GENERIC=m"
- Revert "Drivers: hv: balloon: Add logging for dynamic memory operations"
- Revert "Drivers: hv: balloon: Fix info request to show max page count"
- Revert "Drivers: hv: balloon: Disable hot add when CONFIG_MEMORY_HOTPLUG 
is
  not set"
- Revert "hv: change clockevents unbind tactics"
- Revert "Drivers: hv: vss: Improve log messages."
- Revert "Drivers: hv: utils: Fix the mapping between host version and
  protocol to use"
- Revert "Drivers: hv: utils: reduce HV_UTIL_NEGO_TIMEOUT timeout"
- Revert "vmbus: add support for dynamic device id's"
- Revert "tools: hv: remove unnecessary header files and netlink related 
code"
- Revert "tools: hv: fix a compile warning in snprintf"
- Revert "net: use core MTU range checking in virt drivers"
- Revert "hv_netvsc: fix a race between netvsc_send() and netvsc_init_buf()"
- Revert "net: use core MTU range checking in virt drivers"
- Revert "net: deprecate eth_change_mtu, remove usage"
- Revert "net: centralize net_device min/max MTU checking"
- Revert "hv_netvsc: remove excessive logging on MTU change"
- Revert "scsi: storvsc: Payload buffer incorrectly sized for 32 bit 
kernels."
- Revert "PCI: hv: Use the correct buffer size in new_pcichild_device()"
- Revert "PCI: hv: Fix wslot_to_devfn() to fix warnings on device removal"
- Revert "PCI: hv: Use device serial number as PCI domain"
- [Config] Add uio_hv_generic to modules.ignore for 4.8.0-52.55 abi

 -- Thadeu Lima de Souza Cascardo   Mon, 15 May
2017 21:06:52 -0300

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Launchpad Bug Tracker]

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 "ethernet: use net core MTU range checking in more drivers"
- Revert "Drivers: hv: ring_buffer: count on wrap around mappings in
  get_next_pkt_raw() (v2)"
- Revert "hyperv: Fix spelling of HV_UNKOWN"
- Revert "uio-hv-generic: new userspace i/o driver for VMBus"
- Revert "UBUNTU: [Config] CONFIG_UIO_HV_GENERIC=m"
- Revert "Drivers: hv: balloon: Add logging for dynamic memory operations"
- Revert "Drivers: hv: balloon: Fix info request to show max page count"
- Revert "Drivers: hv: balloon: Disable hot add when CONFIG_MEMORY_HOTPLUG 
is
  not set"
- Revert "hv: change clockevents unbind tactics"
- Revert "Drivers: hv: vss: Improve log messages."
- Revert "Drivers: hv: utils: Fix the mapping between host version and
  protocol to use"
- Revert "Drivers: hv: utils: reduce HV_UTIL_NEGO_TIMEOUT timeout"
- Revert "vmbus: add support for dynamic device id's"
- Revert "tools: hv: remove unnecessary header files and netlink related 
code"
- Revert "tools: hv: fix a compile warning in snprintf"
- Revert "net: use core MTU range checking in virt drivers"
- Revert "hv_netvsc: fix a race between netvsc_send() and netvsc_init_buf()"
- Revert "net: use core MTU range checking in virt drivers"
- Revert "net: deprecate eth_change_mtu, remove usage"
- Revert "net: centralize net_device min/max MTU checking"
- Revert "hv_netvsc: remove excessive logging on MTU change"
- Revert "scsi: storvsc: Payload buffer incorrectly sized for 32 bit 
kernels."
- Revert "PCI: hv: Use the correct buffer size in new_pcichild_device()"
- Revert "PCI: hv: Fix wslot_to_devfn() to fix warnings on device removal"
- Revert "PCI: hv: Use device serial number as PCI domain"
- [Config] Add uio_hv_generic to modules.ignore for 4.8.0-52.55 abi

 -- Thadeu Lima de Souza Cascardo   Mon, 15 May
2017 21:06:52 -0300

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: linux-hwe (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Kleber Sacilotto de Souza]

** 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 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[H.-Dirk Schmitt]

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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[H.-Dirk Schmitt]

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
/etc/systemd/network/10-c42-bslave1.link:MTUBytes=9000
/etc/systemd/network/10-c42-bslave2.link:MTUBytes=9000

After boot the MTU on all these interfaces is 1500.

It needs the command 'ip l set bond0  mtu 9000'
to switch all these interfaces together to jumbo frames. 

Before this bug occurs (e.g.  4.8.0-46), it has been working without
explicitly setting the MTU on the command line.

The same misbehaviour is on a second hardware:
Linux dilbert 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:57:17 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

So the situation is for me:
Jumbo Frames are working again, but there seems to be a conflict with systemd 
229.

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[H.-Dirk Schmitt]

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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Jesse Sung]

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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Kleber Sacilotto de Souza]

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 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-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 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Kleber Sacilotto de Souza]

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 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Dmitrii Shcherbakov]

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 max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Jesse Sung]

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[cellard0or]

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 4.8.0.52.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 MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Dmitrii Shcherbakov]

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-
yakkety.git/commit/?id=5e0bc558603351c8ce573913ba64b16908269b67

There are no HWE packages for non-LTS releases so the fix-commited for
Yakkety belongs to both linux-generic in yakkety and linux-generic-
hwe-16.04 in xenial as I understand it.

$ lsb_release -r
Release:16.04
$ apt update

$ apt show linux-generic-hwe-16.04
Package: linux-generic-hwe-16.04
Version: 4.8.0.52.23  # <--- the same version as in the ubuntu-xenial git repo 
tag
Priority: optional
Section: kernel
Source: linux-meta-hwe
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 10.2 kB
Depends: linux-image-generic-hwe-16.04 (= 4.8.0.52.23), 
linux-headers-generic-hwe-16.04 (= 4.8.0.52.23)
Supported: 5y
Download-Size: 1,808 B
APT-Sources: http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
Description: Complete Generic Linux kernel and headers
 This package will always depend on the latest complete generic Linux kernel
 and headers.

--

Or are you saying that this issue is present in 4.4 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.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[cellard0or]

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.
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[H.-Dirk Schmitt]

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 4.8 / 4.10
  in XENIAL LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Chris Sanders]

** 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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Thadeu Lima de Souza Cascardo]

** 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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[JuanJo Ciarlante]

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 usually
require OOB access to the node, as typically bonded
interfaces are used for both mgmt and data planes.

-- 
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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[H.-Dirk Schmitt]

** 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 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 about this bug go to:
https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs