This kernel bug, is affecting all the container solutions also on Xenial
/ 16.04.1 up to 4.4.0-38.
Lots of people are hitting this on many distributions / container solutions:
https://github.com/docker/docker/issues/5618 (mentions Docker, LXC, kubernetes,
Apparently this was fixed in 12.04 and now reintroduced in 16.04.
Once you get the following dmesg message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
... The only fix is to reboot the host.
What I gathered from the docker issue tracking this, it seems a fix was merged
in net-next very recently:
... and is in mainline now:
As I wasn't sure this thread was tracking Xenial (I just added it to the
list), I'm trying to figure out if Ubuntu is tracking this issue
upstream and can backport it into 16.04's 4.4.0-? branch, as a lot of
container use case start to break down because of this bug for the past
** Bug watch added: github.com/docker/docker/issues #5618
** Bug watch added: github.com/coreos/bugs/issues #254
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
unregister_netdevice: waiting for lo to become free. Usage count
Status in Linux:
Status in linux package in Ubuntu:
Status in linux-lts-utopic package in Ubuntu:
Status in linux-lts-xenial package in Ubuntu:
Status in linux source package in Trusty:
Status in linux-lts-utopic source package in Trusty:
Status in linux-lts-xenial source package in Trusty:
Status in linux source package in Vivid:
Users of kernels that utilize NFS may see the following messages when
shutting down and starting containers:
unregister_netdevice: waiting for lo to become free. Usage count =
This can cause issues when trying to create net network namespace and
thus block a user from creating new containers.
Setup multiple containers in parallel to mount and NFS share, create
some traffic and shutdown. Eventually you will see the kernel message.
Dave's script here:
commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream
I currently running trusty latest patches and i get on these hardware
Ubuntu 3.13.0-43.72-generic 184.108.40.206
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 77
model name : Intel(R) Atom(TM) CPU C2758 @ 2.40GHz
stepping : 8
microcode : 0x11d
cpu MHz : 2400.000
cache size : 1024 KB
physical id : 0
siblings : 8
core id : 7
cpu cores : 8
apicid : 14
initial apicid : 14
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 4799.48
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
somehow reproducable the subjected error, and lxc is working still but
not more managable until a reboot.
managable means every command hangs.
I saw there are alot of bugs but they seams to relate to older version
and are closed, so i decided to file a new one?
I run alot of machine with trusty an lxc containers but only these kind of
machines produces these errors, all
other don't show these odd behavior.
thx in advance
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp