unregister_netdevice: waiting for lo to become free. Usage count
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Incomplete
|
Medium
|
|||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Chris J Arges | ||
Vivid |
Fix Released
|
Medium
|
Chris J Arges | ||
linux-lts-utopic (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
linux-lts-xenial (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Trusty |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
SRU Justification:
[Impact]
Users of kernels that utilize NFS may see the following messages when shutting down and starting containers:
unregister_
This can cause issues when trying to create net network namespace and thus block a user from creating new containers.
[Test Case]
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:
https:/
[Fix]
commit de84d89030fa4ef
--
I currently running trusty latest patches and i get on these hardware and software:
Ubuntu 3.13.0-
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
power management:
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
meno
Related branches
tags: | added: kernel-da-key trusty |
Changed in linux (Ubuntu): | |
importance: | Medium → High |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu): | |
assignee: | Chris J Arges (arges) → Stefan Bader (smb) |
Changed in linux (Ubuntu): | |
assignee: | Stefan Bader (smb) → Chris J Arges (arges) |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Trusty): | |
assignee: | nobody → Chris J Arges (arges) |
Changed in linux (Ubuntu Utopic): | |
assignee: | nobody → Chris J Arges (arges) |
Changed in linux (Ubuntu Vivid): | |
assignee: | nobody → Chris J Arges (arges) |
Changed in linux (Ubuntu Trusty): | |
importance: | Undecided → Critical |
importance: | Critical → Medium |
Changed in linux (Ubuntu Utopic): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Vivid): | |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux (Ubuntu Utopic): | |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Trusty): | |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu): | |
importance: | High → Medium |
description: | updated |
Changed in linux (Ubuntu): | |
assignee: | Chris J Arges (arges) → nobody |
status: | In Progress → Fix Released |
Changed in linux (Ubuntu Trusty): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Utopic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Vivid): | |
status: | In Progress → Fix Committed |
no longer affects: | linux (Ubuntu Utopic) |
no longer affects: | linux-lts-utopic (Ubuntu Vivid) |
tags: | added: verification-needed-trusty |
tags: | added: verification-needed-vivid |
Changed in linux-lts-utopic (Ubuntu Trusty): | |
status: | New → Fix Released |
Changed in linux (Ubuntu Vivid): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu Trusty): | |
status: | Fix Committed → Fix Released |
Changed in linux-lts-utopic (Ubuntu): | |
status: | New → Confirmed |
Changed in linux-lts-utopic (Ubuntu): | |
importance: | Undecided → Medium |
tags: |
added: verification-done-vivid removed: verification-needed-vivid |
tags: |
added: verification-done-trusty removed: verification-needed-trusty |
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Confirmed → Incomplete |
Changed in linux-lts-xenial (Ubuntu Trusty): | |
status: | Confirmed → Won't Fix |
Changed in linux-lts-utopic (Ubuntu): | |
status: | Confirmed → Won't Fix |
Changed in linux-lts-xenial (Ubuntu): | |
status: | Confirmed → Won't Fix |
tags: | added: cscc |
tags: | added: sts |
Hey guys, sorry I don't have the time to put together a proper bug report, but the following GitHub thread has plenty of info about it.
https:/ /github. com/docker/ docker/ issues/ 5618#issuecomme nt-50189996