On Fri, Oct 23, 2009 at 10:07:59AM -0700, Matthew Dillon wrote:
> :By the way, I caught a different panic on vkernel. I think the last
> :I ran `hammer cleanup' on /usr/obj was before applying hammer05.patch
> :or hammer06.patch to vkernel.
> :
> :$ ls /usr/obj
> :build.log t
> :$ rm -rf /usr/obj/*; sync
> :$ panic: assertion: parent != NULL in hammer_cursor_removed_node
> :mp_lock = 00000000; cpuid = 0
> :Trace beginning at frame 0x5b7dfabc
> :panic(5b7dfae0,0,0,58ba7168,5b7dfaf8) at 0x80dadce
> :panic(824684c,8269077,82826b7,5e226588,0) at 0x80dadce
> :hammer_cursor_removed_node(58ba7168,0,0,5b7dfc9c,0) at 0x81fe93a
> :hammer_btree_do_propagation(58ba7168,0,58ba71b8,58ba71b8,58ba71b8) at 0x81fc4e0
> :hammer_btree_do_propagation(0,0,52e22040,b,5b7dfbe8) at 0x81fc4c5
> :hammer_btree_delete(5b7dfc9c,1,1,5b7d0114,52e22040) at 0x81fc8c4
> :hammer_delete_at_cursor(5b7dfc9c,3,50c7fb30,b,4ae1c1b6) at 0x820b74e
> :hammer_ip_delete_record(5b7dfc9c,5e41ead0,50c7fb30,b,4000) at 0x820b9b6
> :hammer_ip_delete_range(5b7dfc9c,5e41ead0,0,0,ffffffff) at 0x820bda0
> :hammer_sync_inode(5b7d0114,5e41ead0,5b7d0000,5b7d0114,5b7d0000) at 0x82029bd
> :hammer_flusher_create(561212f0,0,0,0,0) at 0x8200b47
> :Debugger("panic")
>
> It's possible this will be fixed by the new patch as the propagation
> code uses the recovery mechanism that was patched (I think), or the bug
> fix from the problem corecode reported (also in patch 6). If you
> have that core I'd like to see it, though, to make sure.
The PC caught a panic with a similarly looking backtrace 9 hours after
starting the kernel with hammer06.patch. It's in ~y0netan1/crash on leaf,
as {kernel,vmcore}.11 .