Ok so I have reports that NFS may also be a red herring, however I've
found a patch that seems to greatly mitigate issues when testing with
the reproducer I was provided. So I'm going to provide a test build with
that for 3.13, 3.16, 3.19 and users can give me feedback if that helps.
In addition, if you still can reproduce the issue with this fix, it
would be helpful to know more about your test case. I'd like to handle
any of these issues as a separate bug.
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Trusty)
Importance: Critical => Medium
** Changed in: linux (Ubuntu Utopic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Vivid)
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 changed:
+ SRU Justification:
+
+ [Impact]
+
+ 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 = 1
+
+ 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://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24
+
+ [Fix]
+ commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream
+
+ --
+
I currently running trusty latest patches and i get on these hardware
and software:
Ubuntu 3.13.0-43.72-generic 3.13.11.11
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
