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- xenial' to 'verification-done-xenial'.
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-xenial -- 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/1597867 Title: thunderx nics fail to establish link Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] When connected to certain switches, Cavium ThunderX nodes will occasionally fail to establish a link. On one setup (using a Cisco 10G switch), we're seeing a failure rate of about 20%. Manually reloading the driver modules - or rebooting - is required to recover. A fix is now available in linux-next that greatly reduces (though it doesn't 100% eliminate) the frequency of occurrences (2% vs. 20%, in my case). Investigation continues to identify a resolution for the remaining cases. [Test Case] Connect Cavium ThunderX systems to a known bad switch, and put them in a reboot loop. In my test, I use the maas cli to release/acquire/deploy systems, and wait for a node to enter the deployment failure state. [Regression Risk] The fix is upstream, and internal to a specific driver only used on Cavium ThunderX systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597867/+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
