netbsd boot error: panic: cpu0: softints stuck for NUM seconds (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9799297d00f4 make: trim down code for parsing the :gmtime ..
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=170e6abb180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1420f906d33d9f1f
dashboard link: https://syzkaller.appspot.com/bug?extid=6409a7651c570d4f3d22
compiler: g++ (Debian 12.2.0-14) 12.2.0

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c1b209eb140e/disk-9799297d.raw.xz
netbsd.gdb: https://storage.googleapis.com/syzbot-assets/b8c36680eb31/netbsd-9799297d.gdb.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6409a7...@syzkaller.appspotmail.com

[ 23.0098593] panic: cpu0: softints stuck for 16 seconds
[ 23.0098593] cpu1: found cpu0 heart stopped beating after 16 seconds
[ 23.0098593] cpu0: Begin traceback...
[ 23.0098593] vpanic() at netbsd:vpanic+0x2f0 sys/kern/subr_prf.c:288
[ 23.0098593] panic() at netbsd:panic+0x49 sys/kern/subr_prf.c:1116
[ 23.0098593] usb0 at vhci0: USB revision 2.0
[ 23.0098593] uhub0 at usb0: NetBSD (0x0000) VHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 1
[ 23.0098593] heartbeat() at netbsd:heartbeat+0x7c3 select_patient sys/kern/kern_heartbeat.c:549 [inline]
[ 23.0098593] heartbeat() at netbsd:heartbeat+0x7c3 sys/kern/kern_heartbeat.c:706
[ 23.0098593] hardclock() at netbsd:hardclock+0x1d9 sys/kern/kern_clock.c:348
[ 23.0098593] Xresume_lapic_ltimer() at netbsd:Xresume_lapic_ltimer+0x1e
[ 23.0098593] --- interrupt ---
[ 23.0098593] kcov_silence_leave() at netbsd:kcov_silence_leave+0x96 sys/kern/subr_kcov.c:585
[ 23.0098593] if_slowtimo_intr() at netbsd:if_slowtimo_intr+0x1d0 if_slowtimo_countdown sys/net/if.c:2639 [inline]
[ 23.0098593] if_slowtimo_intr() at netbsd:if_slowtimo_intr+0x1d0 sys/net/if.c:2655
[ 23.0098593] callout_softclock() at netbsd:callout_softclock+0x2ab sys/kern/kern_timeout.c:873
[ 23.0098593] softint_dispatch() at netbsd:softint_dispatch+0x40a softint_execute sys/kern/kern_softint.c:605 [inline]
[ 23.0098593] softint_dispatch() at netbsd:softint_dispatch+0x40a sys/kern/kern_softint.c:848
[ 23.0098593] DDB lost frame for netbsd:Xsoftintr+0x4c, trying 0xffffb1822fa320f0
[ 23.0098593] Xsoftintr() at netbsd:Xsoftintr+0x4c
[ 23.0098593] --- interrupt ---
[ 23.0098593] 0:
[ 23.0098593] cpu0: End traceback...
[ 23.0098593] fatal breakpoint trap in supervisor mode
[ 23.0098593] trap type 1 code 0 rip 0xffffffff80235475 cs 0x8 rflags 0x246 cr2 0 ilevel 0x7 rsp 0xffffb1822fa31c18
[ 23.0098593] curlwp 0xffffa5c6a87c2080 pid 0.5 lowest kstack 0xffffb1822fa2d2c0
Stopped in pid 0.5 (system) at netbsd:breakpoint+0x5: leave
breakpoint() at netbsd:breakpoint+0x5
db_panic() at netbsd:db_panic+0xec sys/ddb/db_panic.c:71
vpanic() at netbsd:vpanic+0x2f0 sys/kern/subr_prf.c:288
panic() at netbsd:panic+0x49 sys/kern/subr_prf.c:1116
heartbeat() at netbsd:heartbeat+0x7c3 select_patient sys/kern/kern_heartbeat.c:549 [inline]
heartbeat() at netbsd:heartbeat+0x7c3 sys/kern/kern_heartbeat.c:706
hardclock() at netbsd:hardclock+0x1d9 sys/kern/kern_clock.c:348
Xresume_lapic_ltimer() at netbsd:Xresume_lapic_ltimer+0x1e
--- interrupt ---
kcov_silence_leave() at netbsd:kcov_silence_leave+0x96 sys/kern/subr_kcov.c:585
if_slowtimo_intr() at netbsd:if_slowtimo_intr+0x1d0 if_slowtimo_countdown sys/net/if.c:2639 [inline]
if_slowtimo_intr() at netbsd:if_slowtimo_intr+0x1d0 sys/net/if.c:2655
callout_softclock() at netbsd:callout_softclock+0x2ab sys/kern/kern_timeout.c:873
softint_dispatch() at netbsd:softint_dispatch+0x40a softint_execute sys/kern/kern_softint.c:605 [inline]
softint_dispatch() at netbsd:softint_dispatch+0x40a sys/kern/kern_softint.c:848
DDB lost frame for netbsd:Xsoftintr+0x4c, trying 0xffffb1822fa320f0
Xsoftintr() at netbsd:Xsoftintr+0x4c
--- interrupt ---
0:
ds 1bd8
es 1c28
fs 10
gs ef4d
rdi 0
rsi 1
--db_more--

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup