On 11/25/2009 01:47 AM, akpm@xxxxxxxxxxxxxxxxxxxx wrote: > The mm-of-the-moment snapshot 2009-11-24-16-47 has been uploaded to Hi, when executing qemu-kvm I often get following warning and a hard lockup. WARNING: at kernel/smp.c:292 smp_call_function_single+0xbd/0x140() Hardware name: To Be Filled By O.E.M. Modules linked in: kvm_intel kvm fuse ath5k ath Pid: 3265, comm: qemu-kvm Not tainted 2.6.32-rc8-mm1_64 #912 Call Trace: [<ffffffff81039678>] warn_slowpath_common+0x78/0xb0 [<ffffffffa007fd50>] ? __vcpu_clear+0x0/0xd0 [kvm_intel] [<ffffffff810396bf>] warn_slowpath_null+0xf/0x20 [<ffffffff8106410d>] smp_call_function_single+0xbd/0x140 [<ffffffffa0080af6>] vmx_vcpu_load+0x46/0x170 [kvm_intel] [<ffffffffa004dd94>] kvm_arch_vcpu_load+0x24/0x60 [kvm] [<ffffffffa0047a8d>] kvm_sched_in+0xd/0x10 [kvm] [<ffffffff8102de37>] finish_task_switch+0x67/0xc0 [<ffffffff814699f8>] schedule+0x2f8/0x9c0 [<ffffffffa0063538>] ? kvm_apic_has_interrupt+0x48/0x90 [kvm] [<ffffffffa0062a58>] ? kvm_cpu_has_interrupt+0x58/0x70 [kvm] [<ffffffffa0047c9d>] kvm_vcpu_block+0x6d/0xb0 [kvm] [<ffffffff81050f60>] ? autoremove_wake_function+0x0/0x40 [<ffffffffa0055a5a>] kvm_arch_vcpu_ioctl_run+0x3fa/0xb80 [kvm] [<ffffffffa0049955>] kvm_vcpu_ioctl+0x435/0x590 [kvm] [<ffffffff8102f4ce>] ? enqueue_entity+0x6e/0xe0 [<ffffffff8102f5eb>] ? enqueue_task_fair+0x3b/0x80 [<ffffffff8102f6c3>] ? task_new_fair+0x93/0x120 [<ffffffff810cd848>] vfs_ioctl+0x38/0xd0 [<ffffffff810cdd8a>] do_vfs_ioctl+0x8a/0x5a0 [<ffffffff81062926>] ? sys_futex+0xc6/0x170 [<ffffffff810ce2ea>] sys_ioctl+0x4a/0x80 [<ffffffff81002eeb>] system_call_fastpath+0x16/0x1b ---[ end trace ced05997e63d4d13 ]--- It is a regression against 2009-11-13-19-59. Any ideas? thanks, -- js -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
