Intel NICs not properly reporting link speed in SysFS in Xenial

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1757191/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 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.16-rc6

Hi Joeseph, I got the tester to try 4.16 and the tests still fail for the same reason. This is the test output indicating that /sys/class/net/DEVICENAME/speed still reports a -1 for the second port.

ERROR:root:Detected link speed (-1) is lower than detected max speed (10000)
ERROR:root:Check your device configuration and try again.
ERROR:root:If you want to override and test despite this under-speed link, use
ERROR:root:the --underspeed-ok option.

And just to verify, dmesg shows we are booted into 4.16:
[ 0.000000] Linux version 4.16.0-041600rc6-generic (kernel@gloin) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #201803182230 SMP Mon Mar 19 02:32:18 UTC 2018
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600rc6-generic root=UUID=fcac9914-96c0-49b0-803b-269db52c3756 ro

Thanks for testing. We now know this bug also exists upstream. Do you happen to know if this is a regression? Was there a prior kernel version that did not exhibit this bug?

It looks like this happened perhaps sometime between 4.10 and 4.13:

4.4.0-112: https://certification.canonical.com/hardware/201802-26096/submission/127640/
Driver: ixgbe (ver: 4.2.1-k)
Shows proper speed for both ports

4.10.0-42: https://certification.canonical.com/hardware/201712-26025/submission/125481/
Driver: ixgbe (ver: 4.4.0-k)
Shows proper speed for both ports

4.13.0-37: https://certification.canonical.com/hardware/201803-26156/submission/128508/
Driver: ixgbe (ver: 5.1.0-k)
Shows -1 for second port

4.16.0-041600rc6 (tester sent via email)
Driver version unknown
Shows -1 for second port

We can perform a bisect to identify the commit that introduced this bug. Would it be possible for the tester to test some kernels? To perform a bisect, we need to identify the last kernel version that did not have the bug and the first version that did. The first kernels to test would be:

v4.11 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/
v4.12 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/

This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.