syzbot


upstream boot error: can't ssh into the instance (8)
Status: closed as invalid on 2021/01/27 17:06
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 273d, last: 273d
similar bugs (9):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream upstream boot error: can't ssh into the instance (5) 1 627d 627d 0/22 closed as invalid on 2020/02/09 07:17
upstream upstream boot error: can't ssh into the instance (2) 45 1004d 1005d 12/22 fixed on 2019/03/06 07:43
upstream upstream boot error: can't ssh into the instance (6) 1 626d 626d 0/22 closed as invalid on 2020/02/10 07:37
upstream upstream boot error: can't ssh into the instance (4) 1 629d 629d 0/22 closed as invalid on 2020/02/07 07:17
upstream upstream boot error: can't ssh into the instance (9) 3 273d 273d 0/22 closed as invalid on 2021/01/28 07:47
upstream upstream boot error: can't ssh into the instance 21 1259d 1299d 0/22 closed as invalid on 2018/06/14 06:16
upstream upstream boot error: can't ssh into the instance (3) 1 841d 841d 0/22 closed as invalid on 2019/07/14 14:27
upstream upstream boot error: can't ssh into the instance (10) 137 169d 256d 0/22 auto-closed as invalid on 2021/07/14 07:15
upstream upstream boot error: can't ssh into the instance (7) 316 372d 614d 0/22 auto-closed as invalid on 2021/01/19 09:15
Crashes (3):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-qemu2-arm64 2021/01/27 13:29 upstream 2ab38c17aac1 a0ebf917 .config log upstream boot error: can't ssh into the instance
ci-qemu2-arm64 2021/01/27 13:29 upstream 2ab38c17aac1 a0ebf917 .config log upstream boot error: can't ssh into the instance
ci-qemu2-arm64 2021/01/27 13:29 upstream 2ab38c17aac1 a0ebf917 .config log upstream boot error: can't ssh into the instance