From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Luming Yu <luming.yu@shingroup.cn>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
mpe@ellerman.id.au, npiggin@gmail.com, jialong.yang@shingroup.cn,
luming.yu@gmail.com
Subject: Re: [PATCH 1/2] powerpc/entry: convert to common and generic entry
Date: Fri, 13 Sep 2024 14:15:40 +0200 [thread overview]
Message-ID: <81200b50-eaec-4cfd-9121-f661f3065572@csgroup.eu> (raw)
In-Reply-To: <F81D1486B7B82141+ZuQp4YQkAA2cB9Rw@HX09040029.powercore.com.cn>
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.
Does it work with ppc64le_defconfig ?
On my side there is absolutely nothing happening after the last line,
the screen remains steady.
Christophe
next prev parent reply other threads:[~2024-09-13 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 8:24 Luming Yu
2024-09-12 9:11 ` Christophe Leroy
2024-09-12 9:35 ` Christophe Leroy
2024-09-12 10:23 ` Christophe Leroy
2024-09-13 1:40 ` Luming Yu
2024-09-13 6:54 ` Christophe Leroy
2024-09-13 7:38 ` Luming Yu
2024-09-13 8:30 ` Christophe Leroy
2024-09-13 12:02 ` Luming Yu
2024-09-13 12:15 ` Christophe Leroy [this message]
2024-09-14 2:22 ` Luming Yu
2024-09-18 13:47 ` Christophe Leroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81200b50-eaec-4cfd-9121-f661f3065572@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=jialong.yang@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luming.yu@gmail.com \
--cc=luming.yu@shingroup.cn \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®