Locking crash in 5.99.22?

Hello!
I've just observed crash with yesterday's kernel:
$ crash -M netbsd.40.core -N netbsd.40
Crash version 5.99.22, image version 5.99.22.
System panicked: dump forced via kernel debugger
Backtrace from time of crash is available.
crash> bt
_KERNEL_OPT_NAGR(100,8,c02c5215,8,c05a0f48,0,c051737c,c05a0f1c,0,eae96864) at 0
_KERNEL_OPT_IPX(100,0,eae96914,c018012a,c010cc0a,0,c05b3185,eae96888,c05b3183,d000063)
at 0xe9402860
db_sifting_cmd(c010cc0a,0,c05b3185,eae96888,c05b3183,d000063,eae968a4,c01748db,2f00,0)
at 0xc017f9d7
db_command(eae96934,c05a0eb0,c067a4be,c010cc0a,0,eae969b0,c05a0eb0,eae96918,eae96954,0)
at 0xc018012a
db_command_loop(c010cc0a,b84,1,e8b3157d,c05e8b80,1,1,ffffff,0,eae96ab0) at
0xc018036d
db_trap(6,0,58,c03bd507,c05dc1a0,1000000,0,c054375c,0,10) at 0xc0185cd0
kdb_trap(6,0,eae96ab0,c010cc0a,8,10246,0,0,eae96a5c,c0387d73) at 0xc0182cc4
trap() at 0xc03dd10e
--- trap (number 6) ---
mutex_enter(eae96ca4,4,0,eae96ccc,0,0,eae96c9c,e9402860,c1e4ff00,2) at
0xc010cc0a
sysctl_dispatch(eae96c9c,6,0,eae96ccc,0,0,eae96c9c,e9402860,c1e4ff00,4b040ab9)
at 0xc0285321
sys___sysctl(e9402860,eae96d00,eae96d28,c030fa31,ccf7adc0,e8b313e0,ca,bfbfe1fc,6,0)
at 0xc0285649
syscall(eae96d48,b3,ab,1f,1f,bfbfe21c,0,bfbfe098,bbb992c4,6) at 0xc03bf756
Related question, is information of this kind helpful?
Is there any way to improve crash reportage?
BTW, is there any way to use debug info from kernel build directory?
Maybe line information?
--
HE CE3OH...