Unable to set jumbo frames on Intel I218-V e1000e

Bug #1685612 reported by Kim Botherway on 2017-04-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Description: Ubuntu 16.10
Release: 16.10
  Installed: 4.8.0-49.52
  Candidate: 4.8.0-49.52
  Version table:
 *** 4.8.0-49.52 500
        500 http://ftp.iinet.net.au/pub/ubuntu yakkety-proposed/main amd64 Packages
        100 /var/lib/dpkg/status

  Installed: 4.8.0-48.51
  Candidate: 4.8.0-48.51
  Version table:
 *** 4.8.0-48.51 500
        500 http://ftp.iinet.net.au/pub/ubuntu yakkety-proposed/main amd64 Packages
        100 /var/lib/dpkg/status

What you expected to happen: Setting the MTU at 9000 has worked fine until a recent kernel version linux-image-4.8.0-48-generic

What happened instead: Setting jumbo MTU fails:

sudo ip link set enp0s25 mtu 9000
RTNETLINK answers: Invalid argument
sudo ip link set enp0s25 mtu 8000
RTNETLINK answers: Invalid argument
sudo ip link set enp0s25 mtu 4000
RTNETLINK answers: Invalid argument

Anything from 1500 and below works OK.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-48-generic 4.8.0-48.51
ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
 /dev/snd/controlC2: kim 2561 F.... pulseaudio
 /dev/snd/controlC1: kim 2561 F.... pulseaudio
 /dev/snd/controlC0: kim 2561 F.... pulseaudio
CurrentDesktop: KDE
Date: Sun Apr 23 22:21:03 2017
HibernationDevice: RESUME=UUID=b0a00311-8fc8-47c6-be25-2af8ed04b867
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-49-generic root=UUID=366887d1-d769-4e79-8c79-343393d78f9a ro rootflags=subvol=@ noprompt persistent verbose splash mtrr_gran_size=64K mtrr_chunk_size=64M vt.handoff=7
 linux-restricted-modules-4.8.0-49-generic N/A
 linux-backports-modules-4.8.0-49-generic N/A
 linux-firmware 1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2016-10-22 (183 days ago)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
dmi.board.name: NUC5i7RYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H73774-101
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i7RYB:rvrH73774-101:cvn:ct3:cvr:

Kim Botherway (dj-dvant) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Kim Botherway (dj-dvant) wrote :

The last version to work correctly was linux-image-4.8.0-46-generic.

Serge Malo (serge-malo) wrote :

I observe the same problem with
Ubuntu 16.04.02, Kernel and Network card Intel X520-DA2 (10GbE)

I don't see that problem with Ubuntu 16.04.02 Kernel

helium (penguinparatrooper) wrote :

I can confirm this on kernel 4.8.0-49.52~16.04.1 with - Intel Corporation Ethernet Connection I217-LM (rev 04). This of course wreaked havoc on my openvswitch implementation.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers