panic: softclock: invalid to_clock: ADDR (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c16771e8b440 repeat less and distinguish beteen format and..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=113847e4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=7e71aa0505e06e4bb6b6

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/527de5471b93/disk-c16771e8.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/b36ecd9be8d4/bsd-c16771e8.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eceb8bfec505/kernel-c16771e8.xz

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

panic: softclock: invalid to_clock: 868889800
Starting stack trace...
panic(ffffffff832fdc99) at panic+0x1ba sys/kern/subr_prf.c:229
softclock(0) at softclock+0x276 sys/kern/kern_timeout.c:755
softintr_dispatch(0) at softintr_dispatch+0xea sys/arch/amd64/amd64/softintr.c:90
Xsoftclock() at Xsoftclock+0x27
_rb_next(ffffffff836446c8,fffffd806e2df0f0) at _rb_next+0x49 sys/kern/subr_tree.c:493
uvmspace_fork(ffff80003c9b5180) at uvmspace_fork+0x41f sys/uvm/uvm_map.c:-1
process_new(ffff80002a8d8a58,ffff80003c9b5180,1) at process_new+0x553 sys/kern/kern_fork.c:279
fork1(ffff80003c964f88,1,ffffffff82e639f0,0,ffff80003c989d70,0) at fork1+0x3e6 sys/kern/kern_fork.c:405
syscall(ffff80003c989e20) at syscall+0x97e mi_syscall sys/sys/syscall_mi.h:-1 [inline]
syscall(ffff80003c989e20) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7c226e8f4d10, count: 247
End of stack trace.


---
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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.