SYZFAIL: posix_spawnp failed

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3dd691bf9970 sys/uvideo: add quriks for Elgato Game Captur..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=125aedf8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=4aa4f4314b9e413ed84f

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cbd07261d2d1/disk-3dd691bf.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/53e5106b2ada/bsd-3dd691bf.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5158f0d541ec/kernel-3dd691bf.xz

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

SYZFAIL: posix_spawnp failed
(errno 35: Resource temporarily unavailable)


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

login: set $lines = 0
login: internal resource failure
Login incorrect
login: set $maxwidth = 0
login: internal resource failure
Login incorrect
login: show panic
login: internal resource failure
Login incorrect
login: trace
login: internal resource failure
Login incorrect
show registers
login: login: internal resource failure
Login incorrect
show proc
login: login: internal resource failure
Login incorrect
ps
login: login: internal resource failure
Login incorrect
show all locks
login: login: internal resource failure
Login incorrect
show malloc
login: login: internal resource failure
Login incorrect
show all pools
login: login: internal resource failure
Login incorrect
machine ddbcpu 0


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