One of my machines running 2.0_BETA crashed sometime in the last 30 minutes,
and this is the trace I got:


breakpoint(c057c258,cd3a3dd8,cd3a3dcc,c037bbbe,cd3a3dd8) at netbsd:breakpoint+0x
4
cpu_Debugger(cd3a3dd8,100,cd3a3dfc,c04164ad,c0586d60) at netbsd:cpu_Debugger+0xb

panic(c0586d60,45a,cd3a3dfc,c041683a,c27dfc00) at netbsd:panic+0xd4
uvm_mapent_alloc(c27dfc00,0,cd3a3e2c,c041618b,c27dfc9c) at netbsd:uvm_mapent_all
oc+0xb5
uvm_map_clip_end(c27dfc00,c0635318,cc898000,c0416351,c27dfc04) at netbsd:uvm_map
_clip_end+0x14
uvm_unmap_remove(c27dfc00,cc897000,cc898000,cd3a3e78,1) at netbsd:uvm_unmap_remo
ve+0x136
uvm_unmap(c27dfc00,cc897000,cc898000,c040eaa8,c060c300) at netbsd:uvm_unmap+0x26

uvm_km_free(c27dfc00,cc897000,1000,c0379a88,c062c460) at netbsd:uvm_km_free+0x2b

uvm_km_free_poolpage1(c27dfc00,cc897000,cd3a3edc,c5289000,c5289fd8) at netbsd:uv
m_km_free_poolpage1+0x29
mclpool_release(c065d120,cc897000,cd3a3efc,c037b74c,c060c300) at netbsd:mclpool_
release+0x17
pool_allocator_free(c065d120,cc897000,cd3a3f30,c03a3c02,c06074e8) at netbsd:pool
_allocator_free+0x20
pool_reclaim(c065d120,0,cdaf0624,cdaf0620,0) at netbsd:pool_reclaim+0x1b7
pool_drain(0,0,cd3a3f8c,c041c47a,c034f233) at netbsd:pool_drain+0x76
uvm_pageout(cd3684a4,0,c06e3010,0,c010030c) at netbsd:uvm_pageout+0x14f
db{0}>
db{0}> mach cpu 1
using CPU 1
db{0}> trace
acquire(c065aa60,ce507ee8,400000,0,600) at netbsd:acquire+0x7f
lockmgr(c065aa60,400002,0,c043fc96,0) at netbsd:lockmgr+0x614
_kernel_proc_lock(da978320,ce507f64,14,c043f75e,e) at netbsd:_kernel_proc_lock+0
x1a
syscall_plain() at netbsd:syscall_plain+0x111
--- syscall (number 93) ---
0x480addc7:
db{0}>

I had to reboot it, but this isn't the first one I've seen.  Should I send-pr
it?

+j
-- 
Jeff Rizzo                                         http://www.redcrowgroup.com/