SYZFAIL: repeatedly failed to execute the program (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 181c8b93219b Use the same system register alias trick as w..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=166215b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=21cfd91b8538f0340aff

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/187ca402b703/disk-181c8b93.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/8216efc8aaf2/bsd-181c8b93.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d8b1f439ecaa/kernel-181c8b93.xz

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

SYZFAIL: repeatedly failed to execute the program
proc=1 req=3045 state=3 status=67 (errno 4: Interrupted system call)


OpenBSD/amd64 (ci-openbsd-main-9.us-central1-b.c.syzkaller.internal) (tty00)

login: set $lines = 0
Password:set $maxwidth = 0
Login incorrect
login: show panic
Password:trace
Login incorrect
login: show registers
Password:show proc
Login incorrect
login: ps
Password:show all locks
Login incorrect
show malloc
login: Password:


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