On 2024-02-05 22:23:16 [+0800], kernel test robot wrote: > kernel test robot noticed "Kernel_panic-not_syncing:No_working_init_found" on: … > ---------------- --------------------------- > fail:runs %reproduction fail:runs > | | | > :20 75% 15:20 dmesg.Kernel_panic-not_syncing:No_working_init_found > :20 75% 15:20 dmesg.boot_failures … > [ 217.931991][ T1] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. Before that, there is: | [ 201.601164][ T219] request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now | [ 201.790029][ T1] Failed to execute /init (error -8) | [ 217.930082][ T1] Starting init: /bin/sh exists but couldn't execute it (error -8) I *think* there is some kind of memory corruption and the init-ELF file isn't recognized. I don't think this related to printk. Did you see similar reports to this one? This is -rc1 based. I'm going to release rc4 based something today with printk mostly unchanged. Will be interesting to see if this comes back or not. Sebastian
