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/


** Tags added: performing-bisect

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
       Status: Confirmed

** Changed in: linux (Ubuntu Bionic)
       Status: Confirmed => Triaged

** Changed in: linux (Ubuntu Bionic)
   Importance: Medium => High

** Changed in: linux (Ubuntu Artful)
   Importance: Medium => High

-- 
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 linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  This was discovered during certification testing of 16.04.4 (I've now
  seen this behaviour at least 2 times)

  A system under test has a 2 port Intel X550 NIC (10Gb)

  Udev reports the NIC as this:
  Category: NETWORK
  Interface: enp94s0f0
  Product: Ethernet Controller 10G X550T
  Vendor: Intel Corporation
  Driver: ixgbe (ver: 5.1.0-k)
  Path: /devices/pci0000:5d/0000:5d:00.0/0000:5e:00.0
  ID:           [8086:1563]
  Subsystem ID: [152d:8a13]

  Ethtool shows this info (this is for the second port, which has the issue)
  Settings for enp94s0f1:
   Supported ports: [ TP ]
   Supported link modes:   100baseT/Full
                           1000baseT/Full
                           10000baseT/Full
   Supported pause frame use: Symmetric
   Supports auto-negotiation: Yes
   Advertised link modes:  100baseT/Full
                           1000baseT/Full
                           10000baseT/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Speed: 10000Mb/s
   Duplex: Full
   Port: Twisted Pair
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   MDI-X: Unknown
   Supports Wake-on: umbg
   Wake-on: g
   Current message level: 0x00000007 (7)
            drv probe link
   Link detected: yes

  Note ethtool shows an active 10Gb link.

  The test tool determines the NIC speed by introspecting the sysfs data
  for each NIC port.  In this case, by looking at
  /sys/class/net/DEVICENAME/speed

  I've now seen this on a couple different NICs using the ixgbe driver.
  The first port will properly show connected link speed in
  /sys/class/net/DEVICENAME/speed but the second port shows -1 in that
  file.

  Because of this, certification tests are failing because the tool
  believes that the link speed is incorrect.

  This current example is using kernel 4.13.0-37.42~16.04.1

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to