On Fri, Jan 04, 2008 at 03:36:49PM +0100, Tobias Nygren wrote: > Looks like something is wrong in xen land. Possibly vmlocking2 related? Yup, my fault. I'll fix it shortly. Andrew > > Started domain test > Loaded initial symtab at 0xc04b4474, strtab at 0xc04e74b0, # entries 12987 > panic: kernel diagnostic assertion "obj == NULL || > mutex_owned(&obj->vmobjlock)" failed: file "/co/src/sys/uvm/uvm_page.c", line > 1076 > Stopped in pid 0.1 (system) at netbsd:breakpoint+0x1: ret > breakpoint(c045f73c,c0425aa5,c0443824,c0443341,434) at netbsd:breakpoint+0x1 > __kernassert(c0425aa5,c0443341,434,c0443824,0) at netbsd:__kernassert+0x39 > uvm_pagealloc_strat(c04b16c0,304000,0,0,3) at netbsd:uvm_pagealloc_strat+0x522 > pmap_growkernel(c8ab6000,c07dd000,82d9000,c0544af4,0) at > netbsd:pmap_growkernel+0x1ab > uvm_map_prepare(c04814e0,c07dd000,82d9000,0,ffffffff) at > netbsd:uvm_map_prepare+0x24b > uvm_map(c04814e0,c0544bd8,82d9000,0,ffffffff) at netbsd:uvm_map+0xc5 > uvm_km_suballoc(c04814e0,c0544bd8,c0544bd4,8000000,2) at > netbsd:uvm_km_suballoc+0x85 > kmeminit(c07bb000,fbc00000,c04b4474,c0544c2c,c02f35f5) at netbsd:kmeminit+0xab > uvm_init(c03bd376,3ff,c04b0da0,c0544c6c,c03ae1cc) at netbsd:uvm_init+0x67 > main(c01001df,c01001e7,0,0,0) at netbsd:main+0x2d > db> xenconscn_getc(): not console >