On Mon, 10 Jan 2011, Kirill A. Shutemov wrote: > Every time I run qemu with KVM enabled I get this in dmesg: > > [ 182.878328] BUG: sleeping function called from invalid context at mm/slub.c:793 > [ 182.878339] in_atomic(): 1, irqs_disabled(): 0, pid: 4992, name: qemu > [ 182.878355] Pid: 4992, comm: qemu Not tainted 2.6.37+ #31 > [ 182.878361] Call Trace: > [ 182.878381] [<c104e317>] ? __might_sleep+0xd0/0xd7 > [ 182.878394] [<c10ec337>] ? slab_pre_alloc_hook.clone.39+0x23/0x27 > [ 182.878404] [<c10ece27>] ? kmem_cache_alloc+0x22/0xc8 > [ 182.878414] [<c1030221>] ? init_fpu+0x44/0x7b fpu_alloc() does call kmem_cache_alloc with GFP_KERNEL although we are in an atomic context. -- 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
