On Fri, Oct 30, 2009 at 06:14:13PM -0700, Matthew Dillon wrote:
>
> :> :$ 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
> :
> :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 .
>
> I'd like the specific core for that one too.
The vmcore file from the real kernel (not vkernel) is already on my
leaf account, as ~y0netan1/crash/vmcore.11, as mentioned in the quoted part.
If you meant the core file from vkernel, I have no idea which signal
I need to send to it. `call dumpsys' won't work inside vkernel, either.
> I'll commit what I have so far.
Hmm... currently I'm running vkernel built from source as of
e4eb09b2 (that is, hammer06.patch unapplied), and I can't reproduce
the panic on this kernel. I'm compiling vkernel from f3a4893b0
and see if I can reproduce this panic again.