multicore boot error: can't ssh into the instance

multicore boot error: can't ssh into the instance

Status: closed as invalid on 2019/04/04 13:27
Reported-by: syzbot+4f32fe934c41a0373d0e@syzkaller.appspotmail.com
First crash: 2393d, last: 2393d

▶ ▼ Similar bugs (5)

Kernel	Title	Rank 🛈	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
openbsd	multicore boot error: can't ssh into the instance (4)	-1				51	1063d	1063d	0/3	auto-obsoleted due to no activity on 2023/01/23 03:19
openbsd	multicore boot error: can't ssh into the instance (3)	-1				15	1910d	1910d	0/3	closed as invalid on 2020/07/30 14:54
openbsd	multicore boot error: can't ssh into the instance (6)	-1				3	564d	564d	0/3	auto-obsoleted due to no activity on 2024/07/04 16:58
openbsd	multicore boot error: can't ssh into the instance (5)	-1				24	624d	624d	0/3	auto-obsoleted due to no activity on 2024/03/27 02:48
openbsd	multicore boot error: can't ssh into the instance (2)	-1				96	2152d	2153d	0/3	closed as invalid on 2019/12/03 06:42

Crashes (6):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2019/04/04 05:54	openbsd	0459b7d7c4b6	6a475fff	.config	console log						ci-openbsd-multicore
2019/04/04 05:54	openbsd	0459b7d7c4b6	6a475fff	.config	console log						ci-openbsd-multicore
2019/04/04 05:54	openbsd	0459b7d7c4b6	6a475fff	.config	console log						ci-openbsd-multicore
2019/04/04 05:39	openbsd	0459b7d7c4b6	6a475fff	.config	console log						ci-openbsd-setuid
2019/04/04 05:39	openbsd	0459b7d7c4b6	6a475fff	.config	console log						ci-openbsd-setuid
2019/04/04 05:39	openbsd	0459b7d7c4b6	6a475fff	.config	console log						ci-openbsd-setuid

* ~~Struck through~~ repros no longer work on HEAD.