← Back to team overview

kernel-packages team mailing list archive

[Bug 1275809] [NEW] (docker/lxc) container restart causes kernel to lockup

 

Public bug reported:

After restarting some 'ghost' docker containers on precise with the
raring-lts kernel, the kernel locks up and shows:

    [1095015.392057] BUG: soft lockup - CPU#0 stuck for 22s! [gunicorn:12804]
    ... (for each core)

Here is the original, more docker focused bug report:
https://github.com/dotcloud/docker/issues/3873

I could reproduce this bug with various kernel versions. I've set the
softlockup_panic=1 kernel parameter to get some stack traces. See this
gist for stack trace for 3.5 and 3.8 kernels (will add 3.11 any minute):
https://gist.github.com/discordianfish/7886354d9a19b2084775

It also contains a small script to reproduce this, although I couldn't
reproduce it in a vagrant VM just our Dell R710 systems so far.

** Affects: linux (Ubuntu)
     Importance: High
         Status: Incomplete


** Tags: precise

-- 
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/1275809

Title:
  (docker/lxc) container restart causes kernel to lockup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After restarting some 'ghost' docker containers on precise with the
  raring-lts kernel, the kernel locks up and shows:

      [1095015.392057] BUG: soft lockup - CPU#0 stuck for 22s! [gunicorn:12804]
      ... (for each core)

  Here is the original, more docker focused bug report:
  https://github.com/dotcloud/docker/issues/3873

  I could reproduce this bug with various kernel versions. I've set the
  softlockup_panic=1 kernel parameter to get some stack traces. See this
  gist for stack trace for 3.5 and 3.8 kernels (will add 3.11 any
  minute): https://gist.github.com/discordianfish/7886354d9a19b2084775

  It also contains a small script to reproduce this, although I couldn't
  reproduce it in a vagrant VM just our Dell R710 systems so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275809/+subscriptions


Follow ups

References