Great. I'm running 2.6.24-2 on my gutsy install now. The KVM problem seems to still exist here, after resuming from suspend KVM doesn't work, and this is what I get in dmesg:
[ 51.774905] Pid: 7650, comm: kvm Tainted: P 2.6.24-2-generic #1 [ 51.774907] RIP: 0010:[<ffffffff88a84a40>] [<ffffffff88a84a40>] :kvm_amd:svm_vcpu_run+0x330/0x350 [ 51.774915] RSP: 0018:ffff8100273d3990 EFLAGS: 00010046 [ 51.774918] RAX: ffff81001582b000 RBX: ffff81001583e000 RCX: 0000000000000000 [ 51.774920] RDX: ffffffff80610828 RSI: 0000000000000000 RDI: ffff81001583e000 [ 51.774923] RBP: ffff81001582e000 R08: ffff81001582b000 R09: ffff810015891000 [ 51.774925] R10: 0000000000000000 R11: 0000000000000001 R12: ffffffff80610828 [ 51.774928] R13: 0000000000000000 R14: 000000000000ae80 R15: 0000000002b57110 [ 51.774931] FS: 00002b727707fc10(0000) GS:ffffffff8059d000(0000) knlGS:00000000f7f0a6b0 [ 51.774934] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [ 51.774936] CR2: 0000000000000008 CR3: 000000002735a000 CR4: 00000000000006e0 [ 51.774938] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 51.774941] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 51.774944] Process kvm (pid: 7650, threadinfo ffff8100273d2000, task ffff8100316a4000) [ 51.774946] Stack: ffff81001583e000 ffff81001582e000 0000000000000000 0000000000000000 [ 51.774951] 000000000000ae80 0000000002b57110 ffffffff88a6a80c 0000000000000000 [ 51.774955] 0000000000000b28 ffff81002af1b840 ffff81001583e000 000000000000ae80 [ 51.774959] Call Trace: [ 51.774981] [<ffffffff88a6a80c>] :kvm:kvm_vcpu_ioctl_run+0xdc/0x460 [ 51.774996] [<ffffffff88a6ae4b>] :kvm:kvm_vcpu_ioctl+0x2bb/0xf20 [ 51.775012] [<ffffffff8033025e>] __make_request+0xde/0x680 [ 51.775021] [<ffffffff8033ec51>] __up_read+0x21/0xb0 [ 51.775030] [<ffffffff80456e50>] do_page_fault+0x1d0/0x840 [ 51.775060] [<ffffffff80452f7f>] thread_return+0x3a/0x57b [ 51.775097] [<ffffffff881ee4d0>] :xfs:xfs_get_blocks+0x0/0x10 [ 51.775100] [<ffffffff8032cdf6>] submit_bio+0x66/0xf0 [ 51.775116] [<ffffffff804551d9>] error_exit+0x0/0x51 [ 51.775129] [<ffffffff8027c1c3>] __rmqueue_smallest+0xd3/0x160 [ 51.775141] [<ffffffff8027c27f>] __rmqueue+0x2f/0x240 [ 51.775152] [<ffffffff8027c4e2>] rmqueue_bulk+0x52/0xb0 [ 51.775156] [<ffffffff8028563d>] zone_statistics+0x7d/0x80 [ 51.775165] [<ffffffff8028563d>] zone_statistics+0x7d/0x80 [ 51.775171] [<ffffffff8027e057>] get_page_from_freelist+0x427/0x660 [ 51.775181] [<ffffffff80277f0d>] find_lock_page+0x3d/0xc0 [ 51.775190] [<ffffffff8033d4d4>] __prop_inc_single+0x24/0x50 [ 51.775206] [<ffffffff80286fea>] __do_fault+0x21a/0x420 [ 51.775229] [<ffffffff80288bb2>] handle_mm_fault+0x1b2/0x7b0 [ 51.775246] [<ffffffff8033ec51>] __up_read+0x21/0xb0 [ 51.775252] [<ffffffff80456e50>] do_page_fault+0x1d0/0x840 [ 51.775259] [<ffffffff802477fe>] recalc_sigpending+0xe/0x40 [ 51.775279] [<ffffffff802b2e3f>] do_ioctl+0x2f/0xa0 [ 51.775285] [<ffffffff802b30d0>] vfs_ioctl+0x220/0x2c0 [ 51.775288] [<ffffffff802477fe>] recalc_sigpending+0xe/0x40 [ 51.775298] [<ffffffff802b3201>] sys_ioctl+0x91/0xb0 [ 51.775310] [<ffffffff8020c34e>] system_call+0x7e/0x83 [ 51.775329] [ 51.775330] [ 51.775331] Code: 48 8b 46 08 48 39 87 08 0e 00 00 0f 85 1c fd ff ff e9 46 fd [ 51.775340] RIP [<ffffffff88a84a40>] :kvm_amd:svm_vcpu_run+0x330/0x350 [ 51.775346] RSP <ffff8100273d3990> [ 51.775348] CR2: 0000000000000008 A minor improvement is that kvm can be kill -9ed now, which means I can at least get rid of it after it fails. I suspect that since we've confirmed this issue over multiple kernel versions that this is something upstream will have to handle? -- KVM dies after resuming from suspend https://bugs.launchpad.net/bugs/163862 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
