On Thu, Aug 25, 2022 at 08:55:12PM +0800, cuigaosheng wrote: > Thanks for your reply. > > While I was debugging the kernel code of linux-next, I start the kernel > with qemu-system-arm with following commands: > > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- vexpress_defconfig > make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j32 > qemu-system-arm -M vexpress-a9 -m 1024M -s -nographic -kernel arch/arm/boot/zImage \ > -dtb arch/arm/boot/dts/vexpress-v2p-ca9.dtb -sd /home/rootfs.sd \ > -append "root=/dev/mmcblk0 rw console=ttyAMA0" > > But it failed, so I tried to locate the cause of the failure and finally found that > it failed from this patch(cad439fc040e crypto: api - Do not create test larvals if manager is disabled)， > logs as follows: > > EXT4-fs (mmcblk0): Cannot load crc32c driver. VFS: Cannot open root > > device "mmcblk0" or unknown-block(179,0): error -80 Please append a > > correct "root=" boot option; here are the available partitions: 1f00 > > 131072 mtdblock0 (driver?) 1f01 32768 mtdblock1 (driver?) b300 32768 > > mmcblk0 driver: mmcblk Kernel panic - not syncing: VFS: Unable to mount > > root fs on unknown-block(179,0) CPU: 0 PID: 1 Comm: swapper/0 Not > > tainted 5.15.0-rc1+ #1 Hardware name: ARM-Versatile Express [<8010f334>] > > (unwind_backtrace) from [<8010b08c>] (show_stack+0x10/0x14) [<8010b08c>] > > (show_stack) from [<8083f2a4>] (dump_stack_lvl+0x40/0x4c) [<8083f2a4>] > > (dump_stack_lvl) from [<8083b210>] (panic+0xf8/0x2f4) [<8083b210>] > > (panic) from [<80b0175c>] (mount_block_root+0x178/0x200) [<80b0175c>] > > (mount_block_root) from [<80b01bac>] (prepare_namespace+0x150/0x18c) > > [<80b01bac>] (prepare_namespace) from [<8084384c>] > > (kernel_init+0x10/0x124) [<8084384c>] (kernel_init) from [<80100130>] > > (ret_from_fork+0x14/0x24) Exception stack(0x8108bfb0 to 0x8108bff8) > > bfa0: ???????? ???????? ???????? ???????? bfc0: ???????? ???????? > > ???????? ???????? ???????? ???????? ???????? ???????? bfe0: ???????? > > ???????? ???????? ???????? ???????? ???????? ---[ end Kernel panic - not > > syncing: VFS: Unable to mount root fs on unknown-block(179,0) ]--- > > In the patch, crypto_alloc_test_larval will return NULL if CONFIG_CRYPTO_MANAGER disabled, so > I checked to see if this change was the cause "EXT4-fs (mmcblk0): Cannot load crc32c driver > ", the success logs does not have this error. > > When I enabled CONFIG_CRYPTO_MANAGER, kernel can be boot successfully. > > Could that be the reason? I would be very grateful if you could give me some advice. Can you please provide the whole .config file? Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
