crash dump issue

[Patrick Welche <prlw1%welche.eu@localhost>]

With today's source on amd64, I essentially

- ran successfully a non-debug kernel
- added DIAGNOSTIC, DEBUG, LOCKDEBUG, UVMHIST
- boot this debug kernel with efi/serial console
- get a panic

[   3.5850040] ZFS filesystem version: 5
Configuring CGD devices.
[   4.5650030] panic: kernel diagnostic assertion "KERNEL_LOCKED_P()" failed: file "../../../../kern/subr_autoconf.c", line 2102 
[   4.5750023] cpu1: Begin traceback...
[   4.5750023] vpanic() at netbsd:vpanic+0x171
[   4.5850023] kern_assert() at netbsd:kern_assert+0x4b
[   4.5850023] config_attach_pseudo() at netbsd:config_attach_pseudo+0x72
[   4.5950021] cgdopen() at netbsd:cgdopen+0x269
[   4.5950021] bdev_open() at netbsd:bdev_open+0x135
[   4.6050021] spec_open() at netbsd:spec_open+0x49f
[   4.6050021] VOP_OPEN() at netbsd:VOP_OPEN+0x3e
[   4.6150021] vn_open() at netbsd:vn_open+0x21c
[   4.6150021] do_open() at netbsd:do_open+0xc7
[   4.6250021] do_sys_openat() at netbsd:do_sys_openat+0x72
[   4.6250021] sys_open() at netbsd:sys_open+0x24
[   4.6350021] syscall() at netbsd:syscall+0x9d
[   4.6350021] --- syscall (number 5) ---
[   4.6450021] netbsd:syscall+0x9d:
[   4.6450021] cpu1: End traceback...
[   4.6450021] fatal breakpoint trap in supervisor mode
[   4.6550021] trap type 1 code 0 rip 0xffffffff8022f7a5 cs 0x8 rflags 0x202 cr2 0x7f7ff7ed947a ilevel 0 rsp 0xffffd8126df8a950
[   4.6650020] curlwp 0xffff9c6f7206c800 pid 869.869 lowest kstack 0xffffd8126df862c0
Stopped in pid 869.869 (cgdconfig) at   netbsd:breakpoint+0x5:  leave
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0x171
kern_assert() at netbsd:kern_assert+0x4b
config_attach_pseudo() at netbsd:config_attach_pseudo+0x72
cgdopen() at netbsd:cgdopen+0x269
bdev_open() at netbsd:bdev_open+0x135
spec_open() at netbsd:spec_open+0x49f
VOP_OPEN() at netbsd:VOP_OPEN+0x3e
vn_open() at netbsd:vn_open+0x21c
do_open() at netbsd:do_open+0xc7
do_sys_openat() at netbsd:do_sys_openat+0x72
sys_open() at netbsd:sys_open+0x24
syscall() at netbsd:syscall+0x9d
--- syscall (number 5) ---
netbsd:syscall+0x9d:
ds          8
es          1
fs          c800
gs          a900
rdi         0
rsi         2d6
rbp         ffffd8126df8a950
db{1}> c   

[   5.2750662] dumping to dev 168,4 (offset=842729382, size=16754146):
[   5.2750662] dump 2513 2512 2511 2510 2509 2508 2507 2506 2505 2504 2503 2502 2501 2500 2499 2498 2497 2496 2495 2494 2493 2492 2491 2490 2489 2488 2487 2486 2485 2484 2483 2482 2481 2480 2479 2478 2477 2476 2475 2474 2473 2472 2471 2470 2469 2468 2467 2466 2465 2464 2463 2462 2461 2460 2459 2458 2457 2456 2455 2454 ,,,
 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 succeeded


but then rebooting with non-debug kernel

...
/etc/rc: WARNING: No crash dump directory; savecore not run.
...
# ls -l /var/crash
total 8
-rw-------  1 root  wheel  2 Feb 25  2020 bounds
-rw-------  1 root  wheel  5 Jul 30  1997 minfree
# cd store/crash
# savecore .
savecore: no core dump


Where did it go? puzzled...


Cheers,

Patrick