On changeset 16395 with debug on, I got: (XEN) Scrubbing Free RAM: ..done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen ) (XEN) Freed 128kB init memory. (XEN) Assertion ''(mfn_x(d->arch.paging.log_dirty.top) < max_page)'' failed at paging.c:272 (XEN) ----[ Xen-3.2-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff828c801905f9>] paging_mark_dirty+0x32/0x302 (XEN) RFLAGS: 0000000000010286 CONTEXT: hypervisor (XEN) rax: 000000000007dbbe rbx: ffff83007cc92100 rcx: 00000000000026b0 (XEN) rdx: 00000000e8000000 rsi: 0000000000078201 rdi: ffff83007cc92100 (XEN) rbp: ffff828c80247dc8 rsp: ffff828c80247d78 r8: ffff828c802192c0 (XEN) r9: 0000000000000040 r10: ffff828c801e8970 r11: 0000000000000246 (XEN) r12: 0000000000078201 r13: ffff8284012c5028 r14: 0000000080000000 (XEN) r15: ffff83007cc92100 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 0000000079031000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from rsp=ffff828c80247d78: (XEN) ffff828c80247db8 0000000000000206 0000000578205067 ffff828c80247f28 (XEN) 0000000000000000 ffff8284012c5028 0000000080000000 ffff8284012c5028 (XEN) 0000000080000000 ffff83007cc92100 ffff828c80247de8 ffff828c80142a4b (XEN) 00000000e8000000 0000000080000001 ffff828c80247e48 ffff828c8014320d (XEN) 0000000000000286 ffff83007ca1e100 0000000004311afa ffff8284012c5040 (XEN) 0000000000000001 0000000080000000 ffff8284012c5028 ffff8284012c5028 (XEN) ffffffff805d9f70 0000000000000000 ffff828c80247e68 ffff828c8013ed29 (XEN) 0000000000078201 ffff83007cc92100 ffff828c80247f08 ffff828c80143e39 (XEN) ffff83007ca1e100 0000000000000001 00007ff000000000 0000000000000000 (XEN) 000000017cc92100 0000000000000000 ffff828c80247f08 0000000000000001 (XEN) 0000000000000003 0000000000078201 0000000000000000 0000000079035067 (XEN) 0000000000079035 ffff83007ca1e100 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 00007d737fdb80b7 ffff828c801bc1bf (XEN) ffffffff8020634a 000000000000001a 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff80599000 0000000080000000 (XEN) 0000000000000246 0000000000007ff0 0000000000000000 0000000000000000 (XEN) 000000000000001a ffffffff8020634a 0000000000000000 0000000000000001 (XEN) ffffffff805d9f70 0000010000000000 ffffffff8020634a 000000000000e033 (XEN) 0000000000000246 ffffffff805d9f58 000000000000e02b 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) Xen call trace: (XEN) [<ffff828c801905f9>] paging_mark_dirty+0x32/0x302 (XEN) [<ffff828c80142a4b>] alloc_page_type+0x54/0x12f (XEN) [<ffff828c8014320d>] get_page_type+0x37e/0x46d (XEN) [<ffff828c8013ed29>] get_page_and_type_from_pagenr+0x35/0xae (XEN) [<ffff828c80143e39>] do_mmuext_op+0x5a6/0x10f3 (XEN) [<ffff828c801bc1bf>] tracing_off+0xb/0x65 (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Assertion ''(mfn_x(d->arch.paging.log_dirty.top) < max_page)'' failed at pag ing.c:272 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... Seems the assert there is not necessary, right? -Xin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
It shouldn''t have been moved to before the paging_mode_log_dirty(d) check. Actually I think the synchronisation between enabling/disabling log-dirty mode and allocating/deallocating the log-dirty bitmap is slightly suspect. I might look at that in a bit more detail next week. -- Keir On 17/11/07 08:17, "Li, Xin B" <xin.b.li@intel.com> wrote:> (XEN) > (XEN) Reboot in five seconds... > > Seems the assert there is not necessary, right? > -Xin_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel