syzbot

 sign-in | mailing list | source | docs | 🏰
🐞 Open [1338]
≡ Subsystems
🐞 Fixed [7130]
🐞 Invalid [18877]
⬇ Missing Backports [220]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
✨ AI
💬 Send us feedback

linux-next boot error: can't ssh into the instance (6)

Status: auto-obsoleted due to no activity on 2023/12/06 06:07
First crash: 971d, last: 970d
▶ ▼ Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next boot error: can't ssh into the instance (2) -1 6 2676d 2676d 0/29 closed as invalid on 2019/06/11 06:33
upstream linux-next boot error: can't ssh into the instance (5) -1 15 1559d 1561d 0/29 auto-closed as invalid on 2022/04/06 18:40
upstream linux-next boot error: can't ssh into the instance (7) -1 18 770d 775d 0/29 auto-obsoleted due to no activity on 2024/06/03 17:58
upstream linux-next boot error: can't ssh into the instance -1 2 3080d 3087d 0/29 closed as invalid on 2018/02/14 13:58
upstream linux-next boot error: can't ssh into the instance (3) -1 6 2389d 2389d 0/29 closed as invalid on 2019/11/19 17:42
upstream linux-next boot error: can't ssh into the instance (4) -1 9 1871d 1843d 0/29 closed as invalid on 2021/05/17 11:46
Crashes (9):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/10/07 06:01 linux-next 0f0fe5040de5 5e837c76 .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/07 06:01 linux-next 0f0fe5040de5 5e837c76 .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/07 06:01 linux-next 0f0fe5040de5 5e837c76 .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/06 17:05 linux-next 0f0fe5040de5 ea12a918 .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/06 17:05 linux-next 0f0fe5040de5 ea12a918 .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/06 17:05 linux-next 0f0fe5040de5 ea12a918 .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/06 05:21 linux-next 0f0fe5040de5 db17ad9f .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/06 05:20 linux-next 0f0fe5040de5 db17ad9f .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
2023/10/06 05:20 linux-next 0f0fe5040de5 db17ad9f .config console log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: can't ssh into the instance
* Struck through repros no longer work on HEAD.