[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [SPAM] Re: kernel BUG at arch/x86/xen/mmu.c:1860! - ideas.
After i enabled those options (i dont use SLUB, i use SLAB) i do no longer encounter any errors.- turn on CONFIG_DEBUG_PAGEALLOC - turn on CONFIG_DEBUG_LIST - turn on CONFIG_DEBUG_KMEMLEAK - turn on CONFIG_JBD_DEBUG, CONFIG_JBD2_DEBUG - turn on CONFIG_SLUB_DEBUG_ON I completed 1000 loops of snapshot/mount/umoun/removesnapshot. Without those options in 2.6.32.35 i hit a different bug earlier today:But you really have to be patient to see some output, because lvremove will hang quite a while: (a "while" beeing the a a roughly the time it takes for: wait 5 min for error, leave office, get coffee, smoke cigarette, goto restroom, return to office, finally see error) kernel: BUG: unable to handle kernel paging request ... kernel: RIP [<ffffffff8100f2bf>] xen_set_pmd+0x2f/0xb0 syslog/dmesg output is attached as crash.2.6.32.35-xen_01 or available at: http://pastebin.com/Ad8MhUzDAfter that happened i did a kernel recompile without rebooting the machine first and encoundeterd system_call_fastpath as last call once more as shown in crash.2.6.32.35-xen_02 or http://pastebin.com/kB38W5mp Maybe this helps, but i think, if anything, this makes it worse as the debug options actually supressed the problem that needs to be debugged. with best regards -- Andreas "andiolsi "Olsowski Attachment:
crash.2.6.32.35-xen_01 Attachment:
crash.2.6.32.35-xen_02 Attachment:
smime.p7s _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |