uvm_fault: NUM TID PID UID PRFLAGS PFLAGS CPU COMMANDNUM(NUM,NUM,NUM,NUM,58b,ADDR) at NUMtimeout_ru

0 views
Skip to first unread message

syzbot

unread,
Feb 15, 2023, 7:35:49 AM2/15/23
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 1e5b016c5082 sync for __syscall removal
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1554ac80c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=978f679a7f25d915f913

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/452af0b271ef/disk-1e5b016c.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/5145fa4f4c7c/bsd-1e5b016c.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/992507fc6105/kernel-1e5b016c.xz

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

kernel: page fault trap, code=0
Stopped at 0 TID PID UID PRFLAGS PFLAGS CPU COMMAND
0(0,0,0,0,58b,fffffd807afa1f08) at 0
timeout_run(fffffd807afa1f08) at timeout_run+0x8b sys/kern/kern_timeout.c:641
softclock_process_kclock_timeout(fffffd807afa1f08,0) at softclock_process_kclock_timeout+0x1c6 sys/kern/kern_timeout.c:666
softclock(0) at softclock+0x11a sys/kern/kern_timeout.c:717
softintr_dispatch(0) at softintr_dispatch+0xd1 sys/arch/amd64/amd64/softintr.c:90
Xsoftclock() at Xsoftclock+0x1f
acpicpu_idle() at acpicpu_idle+0x2ee sys/dev/acpi/acpicpu.c:1206
sched_idle(ffffffff82b9dff0) at sched_idle+0x2ea sys/kern/kern_sched.c:175
end trace frame: 0x0, count: 8
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.


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

syzbot

unread,
May 16, 2023, 8:35:44 AM5/16/23
to syzkaller-o...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages