[Regression] APM Merlin boards fail to recover link after interface down/up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
dann frazier | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
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 ifdown eth0; sudo ifup eth0
3) Ping should recover, but doesn't
[Fix]
commit 84a527a41f38a80
Author: Shaohui Xie <email address hidden>
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.
Changed in linux (Ubuntu Cosmic): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Bionic): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Cosmic): | |
assignee: | dann frazier (dannf) → nobody |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → dann frazier (dannf) |
status: | Incomplete → In Progress |
description: | updated |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
description: | updated |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1785739
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.