netbsd boot error: panic: cnopen: no console device

31 views
Skip to first unread message

syzbot

unread,
Oct 16, 2021, 1:29:29 AM10/16/21
to syzkaller-...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: e43f704b9aaa fix typos in comments.
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=119d9278b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=739e57438eb9ed9e
dashboard link: https://syzkaller.appspot.com/bug?extid=e53c43077e0aee1707b4
compiler: Debian clang version 11.0.1-2

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

[ 6.2354883] panic: cnopen: no console device
[ 6.2354883] cpu0: Begin traceback...
[ 6.2454123] vpanic() at netbsd:vpanic+0xa1b
[ 6.2754104] panic() at netbsd:panic+0x1b3 sys/kern/subr_prf.c:209
[ 6.2954147] cnopen() at netbsd:cnopen+0x29e sys/dev/cons.c:123
[ 6.3254105] cdev_open() at netbsd:cdev_open+0x2a9 sys/kern/subr_devsw.c:871
[ 6.3454107] spec_open() at netbsd:spec_open+0xb27 sys/miscfs/specfs/spec_vnops.c:564
[ 6.3754147] VOP_OPEN() at netbsd:VOP_OPEN+0x21a
[ 6.4054136] vn_open() at netbsd:vn_open+0x1cce sys/kern/vfs_vnops.c:323
[ 6.4254155] do_open() at netbsd:do_open+0x49d sys/kern/vfs_syscalls.c:1728
[ 6.4554147] do_sys_openat() at netbsd:do_sys_openat+0x44b sys/kern/vfs_syscalls.c:1813
[ 6.4854137] sys_open() at netbsd:sys_open+0x13d sys/kern/vfs_syscalls.c:1834
[ 6.5054205] syscall() at netbsd:syscall+0x60c sy_invoke sys/sys/syscallvar.h:94 [inline]
[ 6.5054205] syscall() at netbsd:syscall+0x60c sys/arch/x86/x86/syscall.c:138
[ 6.5159811] --- syscall (number 5) ---
[ 6.5271328] netbsd:syscall+0x60c:
[ 6.5355211] cpu0: End traceback...
[ 6.5355211] fatal breakpoint trap in supervisor mode
[ 6.5355211] trap type 1 code 0 rip 0xffffffff8022288d cs 0x8 rflags 0x282 cr2 0x7c1213e0d960 ilevel 0 rsp 0xffffc180877e7570
[ 6.5560741] curlwp 0xffffc18012125a00 pid 193.193 lowest kstack 0xffffc180877e02c0
Stopped in pid 193.193 (init) at netbsd:breakpoint+0x5: leave
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0xa1b
panic() at netbsd:panic+0x1b3 sys/kern/subr_prf.c:209
cnopen() at netbsd:cnopen+0x29e sys/dev/cons.c:123
cdev_open() at netbsd:cdev_open+0x2a9 sys/kern/subr_devsw.c:871
spec_open() at netbsd:spec_open+0xb27 sys/miscfs/specfs/spec_vnops.c:564
VOP_OPEN() at netbsd:VOP_OPEN+0x21a
vn_open() at netbsd:vn_open+0x1cce sys/kern/vfs_vnops.c:323
do_open() at netbsd:do_open+0x49d sys/kern/vfs_syscalls.c:1728
do_sys_openat() at netbsd:do_sys_openat+0x44b sys/kern/vfs_syscalls.c:1813
sys_open() at netbsd:sys_open+0x13d sys/kern/vfs_syscalls.c:1834
syscall() at netbsd:syscall+0x60c sy_invoke sys/sys/syscallvar.h:94 [inline]
syscall() at netbsd:syscall+0x60c sys/arch/x86/x86/syscall.c:138
--- syscall (number 5) ---
netbsd:syscall+0x60c:
ds 2918
es 3b3
fs 7560
gs 0
rdi 5
rsi 0
rbp ffffc180877e7570
rbx 0
--db_more--


---
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,
Dec 15, 2021, 10:39:19 AM12/15/21
to syzkaller-...@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