kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #118018
[Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
Dave,
Good to know. Hopefully the bisect will implicate the right lines of code in order to find a v3.19+ fix.
--
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/1403152
Title:
unregister_netdevice: waiting for lo to become free. Usage count
Status in The Linux Kernel:
Unknown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Confirmed
Status in linux source package in Utopic:
Confirmed
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions
References