android12-5.4 boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 45a5b53a ANDROID: GKI: Enable CONFIG_X86_X2APIC
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=15169280500000
kernel config: https://syzkaller.appspot.com/x/.config?x=86d9661266033b77
dashboard link: https://syzkaller.appspot.com/bug?extid=4620bc357aa1464b8b26
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4620bc...@syzkaller.appspotmail.com

NET: Registered protocol family 30
tipc: Started in single node mode
NET: Registered protocol family 40
IPI shorthand broadcast: enabled
AVX2 version of gcm_enc/dec engaged.
AES CTR mode by8 optimization enabled
sched_clock: Marking stable (3945129956, 9041798)->(3963227054, -9055300)
registered taskstats version 1
Loading compiled-in X.509 certificates
Key type ._fscrypt registered
Key type .fscrypt registered
Key type fscrypt-provisioning registered
cfg80211: Loading compiled-in X.509 certificates for regulatory database
cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
ALSA device list:
No soundcards found.
VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
0100 8192 ram0
(driver?)
0101 8192 ram1
(driver?)
0102 8192 ram2
(driver?)
0103 8192 ram3
(driver?)
0104 8192 ram4
(driver?)
0105 8192 ram5
(driver?)
0106 8192 ram6
(driver?)
0107 8192 ram7
(driver?)
0108 8192 ram8
(driver?)
0109 8192 ram9
(driver?)
010a 8192 ram10
(driver?)
010b 8192 ram11
(driver?)
010c 8192 ram12
(driver?)
010d 8192 ram13
(driver?)
010e 8192 ram14
(driver?)
010f 8192 ram15
(driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.72-syzkaller-00309-g45a5b53a3536 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1dd/0x24e lib/dump_stack.c:118
panic+0x285/0x750 kernel/panic.c:221
mount_block_root+0x295/0x3b5 init/do_mounts.c:457
prepare_namespace+0x287/0x28c init/do_mounts.c:622
kernel_init_freeable+0x311/0x3df init/main.c:1483
kernel_init+0xd/0x3a0 init/main.c:1381
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:352
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.