Re: panic rebooting yesterday's kernel

[Chuck Silvers <chuq%chuq.com@localhost>]

On Wed, Oct 21, 2020 at 09:26:49AM +0100, Patrick Welche wrote:
> Booted a yesterday's source amd64 kernel, and on reboot
> 
> [ 17037.8583948] unmounting 0xfffffef63b813000 / (/dev/dk14)...
> [ 17037.8583948] forcefully unmounting / (/dev/dk14)...
> [ 17037.8783949] dk14 at wd4 (root) deleted
> [ 17037.8783949] wd4: detached
> [ 17037.8883950] atabus8: detached
> [ 17037.8883950] ahcisata1: detached
> [ 17038.6083908] Kernel lock error: _kernel_lock,244: spinout
> 
> [ 17038.6083908] lock address : 0xffffffff81082f00 type     :               spin
> [ 17038.6083908] initialized  : 0xffffffff80bc8340
> [ 17038.6083908] shared holds :                  0 exclusive:                  1
> [ 17038.6083908] shares wanted:                  0 exclusive:                  3
> [ 17038.6083908] relevant cpu :                  0 last held:                  1
> [ 17038.6083908] relevant lwp : 0xfffffefd19744080 last held: 0xfffffef642bf4280
> [ 17038.6083908] last locked* : 0xffffffff80a42ab1 unlocked : 0xffffffff80323d4c
> [ 17038.6083908] curcpu holds :                  0 wanted by: 0xfffffefd19744080
> 
> [ 17038.6763377] Skipping crash dump on recursive panic
> [ 17038.6816213] panic: LOCKDEBUG: Kernel lock error: _kernel_lock,244: spinout
> [ 17038.6886673] cpu0: Begin traceback...
> [ 17038.6886673] vpanic() at netbsd:vpanic+0x156
> [ 17038.6983892] snprintf() at netbsd:snprintf
> [ 17038.6983892] lockdebug_more() at netbsd:lockdebug_more
> [ 17038.7083890] _kernel_lock() at netbsd:_kernel_lock+0x22a
> [ 17038.7183890] intr_biglock_wrapper() at netbsd:intr_biglock_wrapper+0x14
> [ 17038.7183890] Xhandle_ioapic_edge17() at netbsd:Xhandle_ioapic_edge17+0x6e
> [ 17038.7296195] --- interrupt ---
> [ 17038.7296195] _kernel_lock() at netbsd:_kernel_lock+0x1f8
> [ 17038.7403251] callout_softclock() at netbsd:callout_softclock+0x425
> [ 17038.7483888] softint_dispatch() at netbsd:softint_dispatch+0xf5
> address 0xffffc8025cf990b8 is invalid
> address 0xffffc8025cf990b0 is invalid
> address 0xffffc8025cf990c0 is invalid
> address 0xffffc8025cf990b8 is invalid
> address 0xffffc8025cf990c8 is invalid
> address 0xffffc8025cf990c0 is invalid
> address 0xffffc8025cf990d0 is invalid
> address 0xffffc8025cf990c8 is invalid
> [ 17038.7784674] DDB lost frame for netbsd:Xsoftintr+0x4f, trying 0xffffc8025cf98ff0
> [ 17038.7900680] Xsoftintr() at netbsd:Xsoftintr+0x4f
> [ 17038.7993371] --- interrupt ---
> address 0xffffc8025cf990c8 is invalid
> address 0xffffc8025cf99080 is invalid
> [ 17038.8084475] Bad frame pointer: 0xffffc8025cf98450
> [ 17038.8084475] ffffc8025cf98450:
> [ 17038.8185590] cpu0: End traceback...
> 
> 
> so no ddb either...
> 
> 
> Cheers,
> 
> Patrick

unfortunately there's no information here indicating what the underlying problem is.
I'm looking into changing something to avoid the second panic,
so that if this happens again then you might get a dump next time.

-Chuck