panic: softclock: invalid to_clock: ADDR (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0b4ddc31a5ae X509_verify(): sync with X509_CRL_verify()
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1768468c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=1a4766215e072e4103d3

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ca20d91a109d/disk-0b4ddc31.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/29340d7f6dc9/bsd-0b4ddc31.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c49a840acfa6/kernel-0b4ddc31.xz

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

panic: softclock: invalid to_clock: 1534471090
Starting stack trace...
panic(ffffffff833476d7) at panic+0x1d0 sys/kern/subr_prf.c:229
softclock(0) at softclock+0x2b6 sys/kern/kern_timeout.c:801
softintr_dispatch(0) at softintr_dispatch+0x140 sys/kern/kern_softintr.c:84
dosoftint(0) at dosoftint+0x54 sys/arch/amd64/amd64/intr.c:847
Xsoftclock() at Xsoftclock+0x27
acpicpu_idle() at acpicpu_idle+0x41e sys/dev/acpi/acpicpu_x86.c:1218
sched_idle(ffffffff837ffff0) at sched_idle+0x4d8 sys/kern/kern_sched.c:191
end trace frame: 0x0, count: 250
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.