Re: [PATCH 1/2] powerpc/entry: convert to common and generic entry
From: Luming Yu
Date: Fri Sep 13 2024 - 22:24:44 EST
On Fri, Sep 13, 2024 at 02:15:40PM +0200, Christophe Leroy wrote:
>
>
> Le 13/09/2024 à 14:02, Luming Yu a écrit :
>
> > > ...
> > > 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.
okay
>
> Does it work with ppc64le_defconfig ?
make ppc64le_defconfig
yes, it builds && boots just fine.
the host is a p8 powernv system , the qemu command line is as below:
qemu-system-ppc64 -m 64g -smp 16,cores=4,threads=4 --enable-kvm -nographic -net nic -net tap,ifname=tap0,script=/etc/qemu-ifup-nat,downscript=/etc/qemu-ifdown-nat Downloads/Fedora-Cloud-Base-38-1.6.ppc64le.qcow2
I will try other test configures as well.
>
> On my side there is absolutely nothing happening after the last line, the
> screen remains steady.
>
>
> Christophe
>