netbsd boot error: panic: cpu0: softints stuck for NUM seconds

[syzbot <syzbot+a32764d0afbda389ea16%syzkaller.appspotmail.com@localhost>]

Hello,

syzbot found the following issue on:

HEAD commit:    befa299d8937 doc: ch-ch-changes
git tree:       netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11f5c297a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=739e57438eb9ed9e
dashboard link: https://syzkaller.appspot.com/bug?extid=a32764d0afbda389ea16
compiler:       Debian clang version 15.0.6

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a2e797fcbca9/disk-befa299d.raw.xz
netbsd.gdb: https://storage.googleapis.com/syzbot-assets/51d88a2abea4/netbsd-befa299d.gdb.xz

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

[ 105.0044876] panic: cpu0: softints stuck for 16 seconds
[ 105.0044876] cpu0: Begin traceback...
[ 105.0044876] vpanic() at netbsd:vpanic+0xc9d
[ 105.0044876] panic() at netbsd:panic+0x1b3 sys/kern/subr_prf.c:209
[ 105.0044876] heartbeat() at netbsd:heartbeat+0xbf8
[ 105.0044876] hardclock() at netbsd:hardclock+0x5e5 sys/kern/kern_clock.c:350
[ 105.0044876] Xresume_lapic_ltimer() at netbsd:Xresume_lapic_ltimer+0x1e
[ 105.0044876] --- interrupt ---
[ 105.0044876] _kernel_lock() at netbsd:_kernel_lock+0xacc __SIMPLELOCK_LOCKED_P sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./x86/lock.h:44 [inline]
[ 105.0044876] _kernel_lock() at netbsd:_kernel_lock+0xacc sys/kern/kern_lock.c:266
[ 105.0044876] frag6_fasttimo() at netbsd:frag6_fasttimo+0x56 sys/netinet6/frag6.c:657
[ 105.0044876] pffasttimo() at netbsd:pffasttimo+0x135 sys/kern/uipc_domain.c:770
[ 105.0044876] callout_softclock() at netbsd:callout_softclock+0xf84 sys/kern/kern_timeout.c:862
[ 105.0044876] softint_dispatch() at netbsd:softint_dispatch+0xdd3 softint_execute sys/kern/kern_softint.c:603 [inline]
[ 105.0044876] softint_dispatch() at netbsd:softint_dispatch+0xdd3 sys/kern/kern_softint.c:842
address 0xffffc780aed720b8 is invalid
address 0xffffc780aed720b0 is invalid
address 0xffffc780aed720c0 is invalid
address 0xffffc780aed720b8 is invalid
address 0xffffc780aed720c8 is invalid
address 0xffffc780aed720c0 is invalid
address 0xffffc780aed720d0 is invalid
address 0xffffc780aed720c8 is invalid
[ 105.0044876] DDB lost frame for netbsd:Xsoftintr+0x57, trying 0xffffc780aed71ff0
[ 105.0044876] Xsoftintr() at netbsd:Xsoftintr+0x57
[ 105.0044876] --- interrupt ---
address 0xffffc780aed720c8 is invalid
address 0xffffc780aed72080 is invalid
[ 105.0044876] 66d23d0853d6a73:
[ 105.0044876] cpu0: End traceback...
[ 105.0044876] fatal breakpoint trap in supervisor mode
[ 105.0044876] trap type 1 code 0 rip 0xffffffff8023686d cs 0x8 rflags 0x292 cr2 0 ilevel 0x7 rsp 0xffffc780aed717e8
[ 105.0044876] curlwp 0xffffc7800ebdb080 pid 0.5 lowest kstack 0xffffc780aed6a2c0
Stopped in pid 0.5 (system) at  netbsd:breakpoint+0x5:  leave
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0xc9d
panic() at netbsd:panic+0x1b3 sys/kern/subr_prf.c:209
heartbeat() at netbsd:heartbeat+0xbf8
hardclock() at netbsd:hardclock+0x5e5 sys/kern/kern_clock.c:350
Xresume_lapic_ltimer() at netbsd:Xresume_lapic_ltimer+0x1e
--- interrupt ---
_kernel_lock() at netbsd:_kernel_lock+0xacc __SIMPLELOCK_LOCKED_P sys/arch/amd64/compile/obj/GENERIC_SYZKALLER/./x86/lock.h:44 [inline]
_kernel_lock() at netbsd:_kernel_lock+0xacc sys/kern/kern_lock.c:266
frag6_fasttimo() at netbsd:frag6_fasttimo+0x56 sys/netinet6/frag6.c:657
pffasttimo() at netbsd:pffasttimo+0x135 sys/kern/uipc_domain.c:770
callout_softclock() at netbsd:callout_softclock+0xf84 sys/kern/kern_timeout.c:862
softint_dispatch() at netbsd:softint_dispatch+0xdd3 softint_execute sys/kern/kern_softint.c:603 [inline]
softint_dispatch() at netbsd:softint_dispatch+0xdd3 sys/kern/kern_softint.c:842
--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 syzkaller%googlegroups.com@localhost.

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

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

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

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

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

-- 
You received this message because you are subscribed to the Google Groups "syzkaller-netbsd-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-netbsd-bugs+unsubscribe%googlegroups.com@localhost.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-netbsd-bugs/000000000000db08290603741298%40google.com.