New submission from Joe "Floid" Kanowitz <[email protected]>:
Using 2.4.1 with the lone patch from http://bugs.dragonflybsd.org/issue1583 DragonFly tucker 2.4.1-RELEASE DragonFly v2.4.1.40.ga038d-RELEASE #1: Sat Jan 30 11:57:51 EST 2010 r...@tucker:/usr/obj/usr/src/sys/GENERIC i386 ... I'm not sure when this occurred; possibly during nightly cleanup. The previous evening gave HAMMER a little more stress than usual via a bit of `undo` usage (normally none) which did seem to be turning up transient(?) "ITERATE ENTIRE HISTORY: Unknown error: 0" results similar to http://leaf.dragonflybsd.org/mailarchive/users/2009-09/msg00062.html (but here the HAMMER config is left at the sane defaults). Not intending to poke at them too much unless it relates to the panic here. Couldn't get a dump because I didn't realize I hadn't specified a dumpdev (doh!). db> trace Debugger(c0591d40) at Debugger+0x34 panic(c0576343,c059e4c3,c055d984,11,4000) at panic+0x9f btree_search(d6df38e4,d6df3880,c0483897,d6df38e4,d6df38e4) at btree_search+0x14a hammer_btree_lookup(d6df38e4) at hammer_btree_lookup+0xd9 hammer_btree_first(d6df38e4,c04ad0a7,19792,15,22) at hammer_btree_first+0xd hammer_ioc_rebalance(d6df3a74,d684cdd0,c294ed50,f4240,0) at hammer_ioc_rebalanca hammer_ioctl(d684cdd0,c0c0680f,c294ed50,1,c28a6b28) at hammer_ioctl+0x726 hammer_vop_ioctl(d6df3ad0,c06409c0,d2f80d50,d2f8dc50,0) at hammer_vop_ioctl+0x2f vop_ioctl(d2f80d50,c2a12e28,c0c0680f,c294ed50,1) at vop_ioctl+0x3e vn_ioctl(cfe75b40,c0c0680f,c294ed50,c28a6b28,d6df3cf0) at vn_ioctl+0xe0 mapped_ioctl(4,c0c0680f,bfbff88c,0,d6df3cf0) at mapped_ioctl+0x3e7 sys_ioctl(d6df3cf0,6,0,0,d268c6d8) at sys_ioctl+0x17 syscall2(d6df3d40) at syscall2+0x1ef Xint0x80_syscall() at Xint0x80_syscall+0x36 Task map 0xc0514cec: pmap=0x1e2, nentries=1946206313, version=12061300 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8300c08a fault code = supervisor read, page not present instruction pointer = 0x8:0xc04a5608 stack pointer = 0x10:0xd6df359c frame pointer = 0x10:0xd6df35a8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 19689 (hammer) current thread = pri 42 (CRIT) kernel: type 12 trap, code=0 Stopped at Debugger+0x34: movb $0,in_Debugger.4260 ---------- messages: 8140 nosy: floid status: unread title: panic (trap 12) around btree_search() in 2.4.1-RELEASE _____________________________________________________ DragonFly issue tracker <[email protected]> <http://bugs.dragonflybsd.org/issue1672> _____________________________________________________
