Hello,
syzbot found the following crash on:
HEAD commit: bfb20851 handle @PKG_EXPAT_LIBS@ and @PKG_EXPAT_CFLAGS@.
git tree: netbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=143323ad200000
dashboard link:
https://syzkaller.appspot.com/bug?extid=73d2ebaf3981d641f6fa
userspace arch: amd64
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+73d2eb...@syzkaller.appspotmail.com
[ 207.0469531] panic: kernel diagnostic assertion "usec >= 0 && usec <
1000000" failed:
file "/syzkaller/managers/netbsd/kernel/sys/kern/subr_time.c", line 101
[ 207.0469531] cpu0: Begin traceback...
[ 207.0581306] vpanic() at netbsd:vpanic+0x214
[ 207.0581306] _GLOBAL__sub_D_65535_0_cpu_configure() at
netbsd:_GLOBAL__sub_D_65535_0_cpu_configure
[ 207.0706886] tvtohz() at netbsd:tvtohz+0x167
[ 207.0805436] tstohz() at netbsd:tstohz+0xa7
[ 207.0916624] nanosleep1() at netbsd:nanosleep1+0x1f4
[ 207.1028363] sys_clock_nanosleep() at netbsd:sys_clock_nanosleep+0x10d
[ 207.1140131] sys___syscall() at netbsd:sys___syscall+0xe2
[ 207.1251889] syscall() at netbsd:syscall+0x32e
[ 207.1369665] --- syscall (number 198) ---
[ 207.1369665] 73d2a883f4aa:
[ 207.1369665] cpu0: End traceback...
[ 207.1507321] dumping to dev 4,1 (offset=0, size=0): not possible
[ 207.1507321] rebooting...
SeaBIOS (version 1.8.2-20190122_225043-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 0x000f29c0: 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.