Le 13/09/2024 à 14:02, Luming Yu a écrit :

quoted

...
nothing happens after that.

reproduced with ppc64_defconfig
[    0.818972][    T1] Run /init as init process
[    5.851684][  T240] request_module: modprobe binfmt-4c46 cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[    5.851742][  T240] kworker/u33:18 (240) used greatest stack depth: 13584 bytes left
[    5.860081][  T232] kworker/u33:16 (232) used greatest stack depth: 13072 bytes left
[    5.863145][  T210] kworker/u35:13 (210) used greatest stack depth: 12928 bytes left
[    5.865000][    T1] Failed to execute /init (error -8)
[    5.868897][    T1] Run /sbin/init as init process
[   10.891673][  T315] request_module: modprobe binfmt-4c46 cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[   10.894036][    T1] Starting init: /sbin/init exists but couldn't execute it (error -8)
[   10.901455][    T1] Run /etc/init as init process
[   10.903154][    T1] Run /bin/init as init process
[   10.904747][    T1] Run /bin/sh as init process
[   15.931679][  T367] request_module: modprobe binfmt-4c46 cannot be processed, kmod busy with 50 threads for more than 5 seconds now
[   15.934689][    T1] Starting init: /bin/sh exists but couldn't execute it (error -8)

That's something different, this is because you built a big-endian 
kernel and you are trying to run a little-endian userspace.

Does it work with ppc64le_defconfig ?

On my side there is absolutely nothing happening after the last line, 
the screen remains steady.


Christophe