Re: KVM induced panic on 2.6.38[2367] & 2.6.39
From: Brad Campbell <hidden>
Date: 2011-06-01 06:31:17
Also in:
kvm, lkml
On 01/06/11 12:52, Hugh Dickins wrote:
I guess Brad could try SLUB debugging, boot with slub_debug=P for poisoning perhaps; though it might upset alignments and drive the problem underground. Or see if the same happens with SLAB instead of SLUB.
Not much use I'm afraid. This is all I get in the log [ 3161.300073] ============================================================================= [ 3161.300147] BUG kmalloc-512: Freechain corrupt The qemu process is then frozen, unkillable but reported in state "R" 13881 ? R 3:27 /usr/bin/qemu -S -M pc-0.13 -enable-kvm -m 1024 -smp 2,sockets=2,cores=1,threads=1 -nam The machine then progressively dies until it's frozen solid with no further error messages. I stupidly forgot to do an alt-sysrq-t prior to doing an alt-sysrq-b, but at least it responded to that. On the bright side I can reproduce it at will. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>