[Bug 1210859] Re: kernel panic when restarting containers
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
** Tags removed: regression-potential ** Tags added: regression-updated ** Tags removed: regression-updated ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
Well, this is a bug that was introduced in 3.8.0-28-generic. As 3.8.0-27-generic does not seems to be affected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
Christer Solskogen, would you need a backport to a release prior to Saucy, or may we close this as Status Invalid? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
Not a lxc bug. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
That works too. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
Christer Solskogen, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.6-raring/linux- image-3.8.13-03081306-generic_3.8.13-03081306.201308021435_amd64.deb worked! ** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream-v3.8.13 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
Christer Solskogen, thank you for providing the crash log. Could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.11-rc4 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: needs-crash-log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
from kmsg: <6>[ 75.398771] device vethldju4L entered promiscuous mode <6>[ 75.398896] IPv6: ADDRCONF(NETDEV_UP): vethldju4L: link is not ready <4>[ 75.402908] cgroup: lxc-start (2032) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future. <4>[ 75.403038] cgroup: lxc-start (2032) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future. <4>[ 75.403462] cgroup: lxc-start (2032) created nested cgroup for controller "perf_event" which has incomplete hierarchy support. Nested cgroups may change behavior in the future. <4>[ 75.549405] audit_printk_skb: 21 callbacks suppressed <5>[ 75.549422] type=1400 audit(1376304399.325:18): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 parent=2038 profile="lxc-container-default" name="/var/lib/ureadahead/debugfs/" pid=2080 comm="ureadahead" fstype="debugfs" srcname="none" flags="rw" <4>[ 79.492574] PGD 119599067 PUD 115cce067 PMD 0 <4>[ 79.492813] Modules linked in: veth(F) bridge(F) stp(F) llc(F) kvm_intel kvm ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) xts(F) lrw(F) gf128mul(F) ablk_helper(F) cryptd(F) microcode(F) cirrus ttm virtio_balloon(F) i2c_piix4 drm_kms_helper drm syscopyarea(F) psmouse(F) sysfillrect(F) sysimgblt(F) serio_raw(F) mac_hid lp(F) parport(F) floppy(F) <4>[ 79.493640] Pid: 109, comm: kworker/u:1 Tainted: GF 3.8.0-28-generic #41-Ubuntu Bochs Bochs <4>[ 79.494022] RSP: 0018:8801161c1c98 EFLAGS: 00010246 <4>[ 79.494276] RDX: RSI: 0086 RDI: <4>[ 79.494552] R10: R11: R12: 8801161c1d50 <4>[ 79.494829] FS: () GS:88011fc8() knlGS: <4>[ 79.495100] CR2: 0048 CR3: 000115bfb000 CR4: 000407e0 <4>[ 79.495389] DR3: DR6: 0ff0 DR7: 0400 <4>[ 79.495685] Stack: <4>[ 79.495929] 8801161c1ce0 8801161c1cd8 8801161c1d00 815c652b <4>[ 79.496108] Call Trace: <4>[ 79.496108] [] __dev_close_many+0x7d/0xc0 <4>[ 79.496108] [] rollback_registered_many+0xc8/0x200 <4>[ 79.496108] [] default_device_exit_batch+0xad/0xf0 <4>[ 79.496108] [] cleanup_net+0x110/0x1b0 <4>[ 79.496108] [] worker_thread+0x16e/0x480 <4>[ 79.496108] [] kthread+0xc0/0xd0 <4>[ 79.496108] [] ret_from_fork+0x7c/0xb0 <4>[ 79.496108] Code: c3 0f 1f 44 00 00 e8 5b 4a fd ff 83 83 b8 00 00 00 01 b8 01 00 00 00 5b 5d c3 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 0f ba 6f 48 02 19 c0 85 c0 75 09 80 bf c8 03 00 00 00 75 06 <4>[ 79.496108] RSP <4>[ 79.499438] ---[ end trace 05842dcf327f38ae ]--- <1>[ 79.499651] BUG: unable to handle kernel paging request at ffd8 <4>[ 79.503411] [] ret_from_fork+0x7c/0xb0 <4>[ 79.503411] [] ? kthread_create_on_node+0x120/0x120 <4>[ 79.503411] Code: 00 48 89 e5 5d 48 8b 40 c8 48 c1 e8 02 83 e0 01 c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 87 98 03 00 00 55 48 89 e5 <48> 8b 40 d8 5d c3 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 <1>[ 79.503411] RIP [] kthread_data+0x10/0x20 <4>[ 79.503411] RSP <4>[ 79.503411] CR2: ffd8 <4>[ 79.503411] ---[ end trace 05842dcf327f38af ]--- <1>[ 79.503411] Fixing recursive fault but reboot is needed! <0>[ 104.060002] BUG: soft lockup - CPU#3 stuck for 22s! [lxc-start:2032] <4>[ 104.060002] Modules linked in: veth(F) bridge(F) stp(F) llc(F) kvm_intel kvm ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) xts(F) lrw(F) gf128mul(F) ablk_helper(F) cryptd(F) microcode(F) cirrus ttm virtio_balloon(F) i2c_piix4 drm_kms_helper drm syscopyarea(F) psmouse(F) sysfillrect(F) sysimgblt(F) serio_raw(F) mac_hid lp(F) parport(F) floppy(F) <4>[ 104.060002] CPU 3 <4>[ 104.060002] Pid: 2032, comm: lxc-start Tainted: GF D 3.8.0-28-generic #41-Ubuntu Bochs Bochs <4>[ 104.060002] RIP: 0010:[] [] generic_exec_single+0x82/0xb0 <4>[ 104.060002] RSP: 0018:880117af3c80 EFLAGS: 0202 <4>[ 104.060002] RAX: 000c RBX: 880117af3c50 RCX: 0005 <4>[ 104.060002] RDX: 0001 RSI: 0100 RDI: 0282 <4>[ 104.060002] RBP: 880117af3cb0 R08: 818071a0 R09: 0100 <4>[ 104.060002] R10: 81ce6fc0 R11: 880116755620 R12: 81159209 <4>[ 104.060002] R13: 880117af3c70 R14: 880115e35b00 R15: 7f7cd52cc000 <4>[ 104.060002] FS: 7f7cd52c3740() GS:88011fc6() knlGS: <4>[ 104.060002] CS: 0010 DS: ES: CR0: 80050033 <4>[ 104.060002] CR2: 7f7cd52cc000 CR3: 000115bfb000 CR4: 000407e0 <4>[ 104.060002] DR0: DR1: DR2: <4>[ 104.060002] DR3: DR6: 0ff
[Bug 1210859] Re: kernel panic when restarting containers
Christer Solskogen, could you please capture the crash following https://help.ubuntu.com/community/DebuggingSystemCrash ? ** Tags added: needs-crash-log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
apport information ** Description changed: With 3.8.0-28-generic stopping a container (at least if there under a minute or so it was started) will crash the kernel. To repeat Make sure you have that kernel (release kernel works fine) - its in the raring-proposed. Create a container (with ubuntu template) Start it Stop it Sometimes it will stop the container, but the kernel will crash if you start the container again. --- Architecture: amd64 DistroRelease: Ubuntu 13.04 MarkForUpload: True Package: lxc 0.9.0-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Uname: Linux 3.8.0-28-generic x86_64 UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + --- + AlsaDevices: + total 0 + crw-rw---T 1 root audio 116, 1 Aug 11 23:37 seq + crw-rw---T 1 root audio 116, 33 Aug 11 23:37 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.9.2-0ubuntu8.3 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + 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 + CurrentDmesg: [2.237712] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input2 + DistroRelease: Ubuntu 13.04 + HibernationDevice: RESUME=UUID=099cd2e0-728c-4398-ae38-04bdd8d6a402 + IwConfig: + br0 no wireless extensions. + + eth0 no wireless extensions. + + lono wireless extensions. + Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: Bochs Bochs + MarkForUpload: True + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LANGUAGE=en_US:en + TERM=screen + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 cirrusdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-28-generic root=UUID=563a33ab-fdcc-48b9-a0b9-05d1ce4c2c1f ro quiet + ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 + RelatedPackageVersions: + linux-restricted-modules-3.8.0-28-generic N/A + linux-backports-modules-3.8.0-28-generic N/A + linux-firmware1.106 + RfKill: Error: [Errno 2] No such file or directory + Tags: raring + Uname: Linux 3.8.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + dmi.bios.date: 01/01/2011 + dmi.bios.vendor: Bochs + dmi.bios.version: Bochs + dmi.chassis.type: 1 + dmi.chassis.vendor: Bochs + dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: + dmi.product.name: Bochs + dmi.sys.vendor: Bochs ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1210859/+attachment/3768887/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
Christer Solskogen, could you please execute the following in a terminal: apport-collect -p linux 1210859 ** Tags added: needs-upstream-testing regression-potential ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
It's a bit hard, since this bug crashed the host system completly. But can run that command after the machine boots. It will probably have something in syslog. ** Tags added: apport-collected ** Description changed: With 3.8.0-28-generic stopping a container (at least if there under a minute or so it was started) will crash the kernel. To repeat Make sure you have that kernel (release kernel works fine) - its in the raring-proposed. Create a container (with ubuntu template) Start it Stop it - Sometimes it will stop the container, but the kernel will crash if you - start the container again. + Sometimes it will stop the container, but the kernel will crash if you start the container again. + --- + Architecture: amd64 + DistroRelease: Ubuntu 13.04 + MarkForUpload: True + Package: lxc 0.9.0-0ubuntu3.4 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + Uname: Linux 3.8.0-28-generic x86_64 + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210859] Re: kernel panic when restarting containers
3.8.0-27-generic also works fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210859 Title: kernel panic when restarting containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1210859/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs