android-5.4 boot error: can't ssh into the instance

Status: closed as invalid on 2020/03/30 11:32
Reported-by: syzbot+7494ca86194416cc2906@syzkaller.appspotmail.com
First crash: 2348d, last: 2348d
▶ ▼ Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-54 android-5.4 boot error: can't ssh into the instance (2) -1 3 2202d 2202d 0/2 closed as invalid on 2020/08/18 13:09
android-54 android-5.4 boot error: can't ssh into the instance (3) -1 12 2202d 2202d 0/2 closed as invalid on 2020/08/19 06:50
Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/03/25 16:08 https://android.googlesource.com/kernel/common android-5.4 6d164dd847d1 e8e6c7d2 .config console log ci2-android-5-4-kasan
2020/03/25 16:08 https://android.googlesource.com/kernel/common android-5.4 6d164dd847d1 e8e6c7d2 .config console log ci2-android-5-4-kasan
2020/03/25 16:08 https://android.googlesource.com/kernel/common android-5.4 6d164dd847d1 e8e6c7d2 .config console log ci2-android-5-4-kasan
2020/03/25 12:56 https://android.googlesource.com/kernel/common android-5.4 a94bb98bfb79 41f049cc .config console log ci2-android-5-4-kasan
2020/03/25 12:56 https://android.googlesource.com/kernel/common android-5.4 a94bb98bfb79 41f049cc .config console log ci2-android-5-4-kasan
2020/03/25 12:56 https://android.googlesource.com/kernel/common android-5.4 a94bb98bfb79 41f049cc .config console log ci2-android-5-4-kasan
* Struck through repros no longer work on HEAD.