:On Monday 13 August 2012 15:38:46 Matthew Dillon wrote:
:> If you have a DDB> prompt you can hit the scoll-lock button and then
:> cursor up.
:
:HAMMER(ROOT) recovery check seqno=7a824b53
:recovery range 30000000008735b0-3000000000878e48
:recovery nexto 3000000000878e48 endseqno=7a824c80
:recovery undo 30000000008735b0-3000000000878e48 (22680 bytes)(RW)
:Found REDO_SYNC 30000000008516b0
:Ignoring extra REDO_SYNC records in UNDO/REDO FIFO. (9 times)
:recovery complete
:recovery redo 30000000008735b0-3000000000878e48 (22680 bytes)(RW)
:Find extended redo 30000000008516b0, 139008 exbytes
:panic: lockmgr: LK_RELEASE: no lock held
:cpuid = 0
:
:Pierre
:--
:I believe in Yellow when I'm in Sweden and in Black when I'm in Wales.
Hmm. Well, that's clearly a software bug but I'm not sure what
is causing the lock to be lost. The debugger backtrace isn't
consistent. I would love to get a kernel core out of this but
it's too early in the boot sequence.
Antonio will have a patch for a boot-time tunable that will bypass
the hammer2 recovery code tomorrow sometime.
-Matt
Matthew Dillon
<dil...@backplane.com>
