kernel hard lock on lxc-stop

Bug #1278591 reported by Tamas Papp on 2014-02-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Server crashed during lxc-stop.

I don't have crashdump, only an ipmi console screenshot with half of the oops message.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.25
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
 total 0
 crw-rw---- 1 root audio 116, 1 Feb 8 22:59 seq
 crw-rw---- 1 root audio 116, 33 Feb 8 22:59 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Feb 10 22:39:29 2014
HibernationDevice: RESUME=UUID=6b896e04-76d0-4836-ad53-8f7cd97954ad
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Supermicro X9DR3-F
MarkForUpload: True


ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=8b2c03eb-f52f-471d-8816-40a69e4e2a01 ro
 linux-restricted-modules-3.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic N/A
 linux-firmware 1.116.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install) 07/31/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0a
dmi.board.asset.tag: To be filled by O.E.M. X9DR3-F
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789: X9DR3-F
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

Tamas Papp (tomposmiko) wrote :
Tamas Papp (tomposmiko) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Did this just start happening after a recent update or upgrade? Was there a prior kernel that did not exhibit this bug?

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Tamas Papp (tomposmiko) wrote :

No, it was running for weeks or so.
Otherwise it's a fresh install, so I don't know, if there was any kernel without this bug.

Tamas Papp (tomposmiko) wrote :

It happened again, ipmi console is captured and attached.

Unfortunately apport wasn't installed on the machine.

It's running Trusty.

Serge Hallyn (serge-hallyn) wrote :

commit 945b2b2d259d1a4364a2799e80e8ff32f8c6ee6f ?

Joseph Salisbury (jsalisbury) wrote :

Do you have a way to reproduce the oops? If so, I can perform a cherry-pick of commit 945b2b2d259d1a4364a2799e80e8ff32f8c6ee6f and build a test kernel.

Changed in linux (Ubuntu Trusty):
status: New → Confirmed
importance: Undecided → High
Joseph Salisbury (jsalisbury) wrote :

You could also test the mainline kernel, which has commit 945b2b2 and see if it resolves this bug. It can be downloaded from:

Tamas Papp (tomposmiko) wrote :

Not really, this was the second case I encountered it in a very long time.
My guess is that it could be reproduced in reasonable time with moderate network traffic and a bunch of lxc-start/stop. After a while it should happen.

Anyway reading the commit message it's very probable, that this commit will fix this issue.

Tamas Papp (tomposmiko) wrote :

I just faced it again.
Joseph, do you have a confirmation, if it fixes this issue?
If so, it could be backported to the LTS kernel...

It's really annoying and LXC is hard to "sell" anyone, if the host machine goes down from time to time.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.