Hello,
syzbot found the following crash on:
HEAD commit: 92d3cba1c669 It seems EEE support is not only on 8211F bu..
git tree: netbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=14735314c00000
dashboard link:
https://syzkaller.appspot.com/bug?extid=0109e9607860acdd554b
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+0109e9...@syzkaller.appspotmail.com
[ 130.0278741] fatal integer divide fault in supervisor mode
[ 130.0278741] trap type 8 code 0 rip 0xffffffff80ee4614 cs 0x8 rflags
0x10246 cr2 0x7e8be98abff8 ilevel 0x8 rsp 0xffffc2816db77d40
[ 130.0278741] curlwp 0xffffc2800f692960 pid 0.23 lowest kstack
0xffffc2816db702c0
[ 130.0278741] panic: trap
[ 130.0278741] cpu1: Begin traceback...
[ 130.0391586] vpanic() at netbsd:vpanic+0x214
[ 130.0391586] snprintf() at netbsd:snprintf
[ 130.0504526] startlwp() at netbsd:startlwp
[ 130.0617515] alltraps() at netbsd:alltraps+0xb2
[ 130.0730456] callout_softclock() at netbsd:callout_softclock+0x237
[ 130.0843412] softint_dispatch() at netbsd:softint_dispatch+0x23e
[ 130.0956364] DDB lost frame for netbsd:Xsoftintr+0x5a, trying
0xffffc2816db77ff0
[ 130.1069329] Xsoftintr() at netbsd:Xsoftintr+0x5a
[ 130.1182302] --- interrupt ---
[ 130.1182302] 0:
[ 130.1182302] cpu1: End traceback...
[ 130.1182302] dumping to dev 4,1 (offset=0, size=0): not possible
[ 130.1295245] 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.