Hello,
syzbot found the following crash on:
HEAD commit: af876e934dda Register kUBSan and KCOV in kernel=GENERIC of..
git tree: netbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=122cda70c00000
dashboard link:
https://syzkaller.appspot.com/bug?extid=d58da99969f58c1a024a
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+d58da9...@syzkaller.appspotmail.com
login: [ 30.2131742] panic: kernel diagnostic assertion "c->c_cpu->cc_lwp
== curlwp || c->c_cpu->cc_active != c" failed:
file "/syzkaller/managers/netbsd/kernel/sys/kern/kern_timeout.c", line 318
[ 30.2131742] cpu0: Begin traceback...
[ 30.2131742] vpanic() at netbsd:vpanic+0x214
[ 30.2231746] _GLOBAL__sub_D_65535_0_cpu_configure() at
netbsd:_GLOBAL__sub_D_65535_0_cpu_configure
[ 30.2231746] callout_destroy() at netbsd:callout_destroy+0xcb
[ 30.2331744] itimerfree() at netbsd:itimerfree+0x102
[ 30.2331744] timers_free() at netbsd:timers_free+0x172
[ 30.2431753] exit1() at netbsd:exit1+0x276
[ 30.2531705] sys_exit() at netbsd:sys_exit+0x6c
[ 30.2631716] syscall() at netbsd:syscall+0x30e
[ 30.2631716] --- syscall (number 1) ---
[ 30.2731703] 79b2b7cfe47a:
[ 30.2731703] cpu0: End traceback...
[ 30.2731703] dumping to dev 4,1 (offset=0, size=0): not possible
[ 30.2731703] rebooting...
SeaBIOS (version 1.8.2-20181029_212248-google)
Total RAM Size = 0x00000001e0000000 = 7680 MiB
CPUs found: 2 Max CPUs supported: 2
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0
removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f2a00: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Booting from Hard Disk 0...
>> NetBSD/x86 BIOS Boot, Revision 5.10 (Tue Jul 17 14:59:51 UTC 2018) (from
>> NetBSD 8.0)
>> Memory:
639/3144640 k
1. Boot normally
2. Boot single user
3. Disable ACPI
4. Disable ACPI and SMP
5. Drop to boot prompt
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.