Oh oops, didn't realize this was the patch with the
751eb6b6042a596b0080967c1a529a9fe98dac1d commit Paul mentionned.

Well, if that made it into Ubuntu's kernel before and including
4.4.0-42, it didn't fix it (I still get the bug on many machines & VMs).

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:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
Status in linux-lts-xenial package in Ubuntu:
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:


  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.

  [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:

  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream


  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic

  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


To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to