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
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:
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?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
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 (1)
ERROR:root:Check
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
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1757191
Title:
Intel NICs not properly reporting link speed in SysFS in Xenial
Status in
6 matches
Mail list logo
