syzbot

 sign-in | mailing list | source | docs
🐞 Open [1026] 🐞 Fixed [3373] 🐞 Invalid [6475]

upstream boot error: can't ssh into the instance (3)
Status: closed as invalid on 2019/07/14 14:27
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 801d, last: 801d
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 586d 586d 0/22 closed as invalid on 2020/02/09 07:17
upstream upstream boot error: can't ssh into the instance (2) 45 964d 964d 12/22 fixed on 2019/03/06 07:43
upstream upstream boot error: can't ssh into the instance (6) 1 585d 585d 0/22 closed as invalid on 2020/02/10 07:37
upstream upstream boot error: can't ssh into the instance (4) 1 588d 588d 0/22 closed as invalid on 2020/02/07 07:17
upstream upstream boot error: can't ssh into the instance (9) 3 233d 233d 0/22 closed as invalid on 2021/01/28 07:47
upstream upstream boot error: can't ssh into the instance 21 1219d 1258d 0/22 closed as invalid on 2018/06/14 06:16
upstream upstream boot error: can't ssh into the instance (8) 3 233d 233d 0/22 closed as invalid on 2021/01/27 17:06
upstream upstream boot error: can't ssh into the instance (10) 137 129d 215d 0/22 auto-closed as invalid on 2021/07/14 07:15
upstream upstream boot error: can't ssh into the instance (7) 316 331d 573d 0/22 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-gce-leak 2019/07/09 12:59 upstream 5ad18b2e60b7 f62e1e85 .config log