syzbot


upstream boot error: can't ssh into the instance (9)
Status: closed as invalid on 2021/01/28 07:47
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 186d, last: 186d
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 539d 539d 0/22 closed as invalid on 2020/02/09 07:17
upstream upstream boot error: can't ssh into the instance (2) 45 917d 917d 12/22 fixed on 2019/03/06 07:43
upstream upstream boot error: can't ssh into the instance (6) 1 538d 538d 0/22 closed as invalid on 2020/02/10 07:37
upstream upstream boot error: can't ssh into the instance (4) 1 541d 541d 0/22 closed as invalid on 2020/02/07 07:17
upstream upstream boot error: can't ssh into the instance 21 1172d 1211d 0/22 closed as invalid on 2018/06/14 06:16
upstream upstream boot error: can't ssh into the instance (8) 3 186d 186d 0/22 closed as invalid on 2021/01/27 17:06
upstream upstream boot error: can't ssh into the instance (3) 1 754d 754d 0/22 closed as invalid on 2019/07/14 14:27
upstream upstream boot error: can't ssh into the instance (10) 137 82d 168d 0/22 auto-closed as invalid on 2021/07/14 07:15
upstream upstream boot error: can't ssh into the instance (7) 316 284d 526d 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-arm32 2021/01/27 20:02 upstream 76c057c84d28 1fa053ad .config log upstream boot error: can't ssh into the instance
ci-qemu2-arm32 2021/01/27 20:02 upstream 76c057c84d28 1fa053ad .config log upstream boot error: can't ssh into the instance
ci-qemu2-arm32 2021/01/27 20:02 upstream 76c057c84d28 1fa053ad .config log upstream boot error: can't ssh into the instance