syzbot


upstream boot error: can't ssh into the instance (12)

Status: closed as invalid on 2021/12/20 10:22
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 350d, last: 350d
similar bugs (11):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream upstream boot error: can't ssh into the instance (11) 5 453d 479d 0/24 auto-closed as invalid on 2021/12/05 08:10
upstream upstream boot error: can't ssh into the instance (5) 1 1028d 1028d 0/24 closed as invalid on 2020/02/09 07:17
upstream upstream boot error: can't ssh into the instance (2) 45 1405d 1406d 12/24 fixed on 2019/03/06 07:43
upstream upstream boot error: can't ssh into the instance (6) 1 1027d 1027d 0/24 closed as invalid on 2020/02/10 07:37
upstream upstream boot error: can't ssh into the instance (4) 1 1030d 1030d 0/24 closed as invalid on 2020/02/07 07:17
upstream upstream boot error: can't ssh into the instance (9) 3 674d 674d 0/24 closed as invalid on 2021/01/28 07:47
upstream upstream boot error: can't ssh into the instance 21 1660d 1700d 0/24 closed as invalid on 2018/06/14 06:16
upstream upstream boot error: can't ssh into the instance (8) 3 674d 674d 0/24 closed as invalid on 2021/01/27 17:06
upstream upstream boot error: can't ssh into the instance (3) 1 1242d 1242d 0/24 closed as invalid on 2019/07/14 14:27
upstream upstream boot error: can't ssh into the instance (10) 137 570d 657d 0/24 auto-closed as invalid on 2021/07/14 07:15
upstream upstream boot error: can't ssh into the instance (7) 316 773d 1015d 0/24 auto-closed as invalid on 2021/01/19 09:15
Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-root 2021/12/18 09:08 upstream 9eaa88c7036e 44068e19 .config log upstream boot error: can't ssh into the instance
* Struck through repros no longer work on HEAD.