'unregister_netdevice: waiting for lo to become free. Usage count = 2' is reported and causing kernel hang when floodlight tests are run using utah
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When utah client is used to run floodlight smoke tests for saucy server images, the following error is reported.
May 13 03:51:09 utah-8671-
May 13 03:51:19 utah-8671-
...
...
May 13 03:54:33 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
May 13 03:54:35 utah-8671-
...
=======
This is observed to occur only when utah is used to run the floodlight smoke tests. Running the floodlight tests without utah does not cause this issue and using utah to run some other tests does not cause this issue either.
Noticed a similar bug 1021471, but this one is occurring in KVM using libvirt.
The issue is only with the saucy kernel version, 3.9.0-1 and does not occur with 3.9.0-0. The tests were tried with saucy server VMs on precise as well as saucy hosts and the results is the same.
Steps to reproduce:
1. Install a default saucy server on a vm (either manually or preseeded default installation) with either i386 or amd64 image using KVM, libvirt
2. Do the following to install utah inside the VM
sudo apt-add-repository -y ppa:utah/stable
sudo apt-get update
sudo apt-get install utah
3. Run the floodlight tests using
sudo utah -r lp:ubuntu-test-cases/server/runlists/floodlight.run
4. Now "kernel: [ 358.452029] unregister_
Install and boot time syslogs are attached.
The impacted jobs are,
https:/
and
https:/
Changed in utah: | |
importance: | Undecided → High |
description: | updated |
no longer affects: | utah |
Could you please run apport-collect 1179509 from the system after this happens?
This sounds like a regression - there was a similar bug around 3.5 or so, but that was fixed upstream.