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 the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- 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/1785739 Title: [Regression] APM Merlin boards fail to recover link after interface down/up Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] On an APM Merlin (X-Gene2) board, the onboard 1G interface fails to re-establish link when the interface is brought down and back up. Juju + MAAS provider does this after every install (so to configure a bridge), making this config unusable. This was actually a regression introduced by the fix for LP: #1632739 in 4.4.0-48.69. [Test Case] 1) From a remote system, start a ping to the IP address of the Merlin board's eth0 interface. 2) On the merlin board: sudo ifconfig eth0 down; sudo ifconfig eth0 up 3) Ping should recover, but doesn't [Fix] commit 84a527a41f38a80353f185d05e41b021e1ff672b Author: Shaohui Xie <shaohui....@nxp.com> Date: Tue May 10 17:42:26 2016 +0800 net: phylib: fix interrupts re-enablement in phy_start [Regression Risk] The fix appears to be straightforward - don't enable interrupts on a phy that does not have a valid interrupt. Fixes are upstream, so any regressions should get upstream support for fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785739/+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
