Using bisection, I've determined that this was introduced in the
following xenial commit:
commit 69747b70c731cc7081e7d13a0f536bb451f5a385
Author: Iyappan Subramanian <isubraman...@apm.com>
Date: Mon Jul 25 17:12:42 2016 -0700
drivers: net: xgene: Enable MDIO driver
--
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/1722579
Title:
xgene nic unresponsive after ifdown/ifup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722579/+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
