assert "dtlookup(unit) == NULL" failed in dt_dev.c (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6c7eb53ac00b Add JH7110 I2C clocks.
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=12ae4c61a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=e1d3eb641938943061e4

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5a5f397e36de/disk-6c7eb53a.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/01cec971f4c6/bsd-6c7eb53a.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3ec40d75fb93/kernel-6c7eb53a.xz

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

panic: kernel diagnostic assertion "dtlookup(unit) == NULL" failed: file "/syzkaller/managers/main/kernel/sys/dev/dt/dt_dev.c", line 168
Starting stack trace...
panic(ffffffff827751d3) at panic+0x159 sys/kern/subr_prf.c:229
__assert(ffffffff827f20dd,ffffffff82814608,a8,ffffffff8279588d) at __assert+0x29 sys/kern/subr_prf.c:157
dtopen(11e5f,11,2000,ffff800021707138) at dtopen+0x1d4 sys/dev/dt/dt_dev.c:168
spec_open_clone(ffff8000281f69c8) at spec_open_clone+0x208
spec_open(ffff8000281f69c8) at spec_open+0x401 sys/kern/spec_vnops.c:148
VOP_OPEN(fffffd807445a128,11,fffffd807f7d7820,ffff800021707138) at VOP_OPEN+0x70 sys/kern/vfs_vops.c:138
vn_open(ffff8000281f6c18,11,0) at vn_open+0x452 sys/kern/vfs_vnops.c:177
doopenat(ffff800021707138,ffffff9c,200000c0,10,0,ffff8000281f6df0) at doopenat+0x26e sys/kern/vfs_syscalls.c:1126
syscall(ffff8000281f6e70) at syscall+0x4a8 sys/arch/amd64/amd64/trap.c:623
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xe89b4b6e930, count: 247
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.