5942 2014-03-11 09:23:49 +0000 [1.4.3] Kernel panic on qemux86-64 when using runqemu kvm option on Ubuntu 13.10 2014-03-20 03:12:31 +0000 1 1 6 Yocto Project Subprojects Kernel linux-yocto 1.4.3 x86 Multiple VERIFIED FIXED Medium+ normal 1.4.3 1 yi.zhao bluelightning alexandru.c.georgescu bluelightning ke.zou sgw yi.zhao --- Regression (Found by QA test) No (bug/feature does not impact docs) oldest_to_newest 41063 0 yi.zhao 2014-03-11 09:23:49 +0000 Image Location: http://autobuilder.yoctoproject.org/pub/nightly/20140306-3/machines/qemu Git rev: dylan/7ab82abcad9ede847c42c01d2a4f4c2c18877e6f This issue is same with bug 3908 which had been fixed in 1.5 and 1.6. But still exists in 1.4. runqemu qemux86-64 bzImage-qemux86-64.bin core-image-minimal-qemux86-64.ext3 kvm ######################## smpboot: CPU0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz (fam: 06, model: 0f, stepping: 0b) Performance Events: general protection fault: 0000 [#1] PREEMPT SMP Modules linked in: CPU 0 Pid: 1, comm: swapper/0 Not tainted 3.8.11-yocto-standard #1 Bochs Bochs RIP: 0010:[<ffffffff81ccbce9>] [<ffffffff81ccbce9>] intel_pmu_init+0x2e5/0x78d RSP: 0000:ffff88000791dde8 EFLAGS: 00000202 RAX: 0000000000000003 RBX: 0000000000000000 RCX: 0000000000000345 RDX: 0000000000000003 RSI: 000000ffffffffff RDI: ffffffff81ca5f90 RBP: ffff88000791de08 R08: 0000000000000007 R09: ffffffff81ca5e20 R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff81ccb09e R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880007c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000001c0b000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper/0 (pid: 1, threadinfo ffff88000791c000, task ffff880007920000) Stack: 0000050300000100 0000000007280202 0000000000000000 ffffffff81d5c038 ffff88000791de38 ffffffff81ccb0d0 0000000000000018 000000000000b010 ffffffff81d5c038 ffffffff81ccb09e ffff88000791de68 ffffffff810002f2 Call Trace: [<ffffffff81ccb0d0>] init_hw_perf_events+0x32/0x3ec [<ffffffff81ccb09e>] ? check_bugs+0x2d/0x2d [<ffffffff810002f2>] do_one_initcall+0x122/0x170 [<ffffffff81cc3c17>] kernel_init_freeable+0x9e/0x201 [<ffffffff816a23e7>] ? _raw_spin_unlock_irq+0x17/0x40 [<ffffffff8106b27b>] ? finish_task_switch+0x5b/0xc0 [<ffffffff8168bed0>] ? rest_init+0x80/0x80 [<ffffffff8168bede>] kernel_init+0xe/0xf0 [<ffffffff816a9ddc>] ret_from_fork+0x7c/0xb0 [<ffffffff8168bed0>] ? rest_init+0x80/0x80 Code: 00 00 0f 46 c8 ff ca 89 0d 75 a2 fd ff 7e 2e 8a 55 e4 b8 03 00 00 00 b9 45 03 00 00 83 e2 1f 83 fa 02 0f 4f c2 89 05 97 a1 fd ff <0f> 32 48 c1 e2 20 89 c0 48 09 c2 48 89 15 1d a2 fd ff e8 d0 a9 RIP [<ffffffff81ccbce9>] intel_pmu_init+0x2e5/0x78d RSP <ffff88000791dde8> ---[ end trace c3b90f5575c6e21b ]--- Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ########################### 41088 1 bluelightning 2014-03-11 15:27:21 +0000 A backport of b8819b02dc4ff29d678cc55887dfe6c2d109a67d should solve this in theory. 41308 2 bluelightning 2014-03-17 10:11:15 +0000 Fix merged to the dylan branch: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dylan&id=2a07edd04ca9a85273de852e2d10aad6dd08d5a2 41481 3 yi.zhao 2014-03-20 03:12:31 +0000 Verified with 1.4.3 rc4 git rev: dylan/c397b69e681d5f1ffe0a0bfd9d43ee880fc27553