xgene nic unresponsive after ifdown/ifup

Bug #1722579 reported by dann frazier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
dann frazier
Xenial
Undecided
dann frazier

Bug Description

[Impact]
Sean Feole discovered that if you ifdown/ifup the NIC on an X-Gene 2 system, the NIC does not come back online. While the interface is reported as up, you cannot ping the system. In addition to the obvious problems this causes for a sysadmin, it also breaks software that does this automatically, such as juju when it sets up a host bridge.

[Test Case]
Boot an X-Gene 2 system, and start pinging it from a remote system. Assuming the pinged interface is eth0, run:

$ sudo ifdown eth0; sudo ifup eth0

System will cease responding to pings.

[Regression Risk]
(Still under investigation)

Revision history for this message
dann frazier (dannf) wrote :

Using bisection, I've determined that this was introduced in the following xenial commit:

commit 69747b70c731cc7081e7d13a0f536bb451f5a385
Author: Iyappan Subramanian <email address hidden>
Date: Mon Jul 25 17:12:42 2016 -0700

    drivers: net: xgene: Enable MDIO driver

Changed in linux (Ubuntu Xenial):
assignee: nobody → dann frazier (dannf)
status: New → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers