From: "Mark Brown" <broonie@kernel.org>
To: Guenter Roeck <groeck@google.com>
Cc: kernelci@groups.io, Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: aarch64 Big Endian
Date: Tue, 6 Aug 2019 21:08:09 +0100 [thread overview]
Message-ID: <20190806200809.GI4527@sirena.org.uk> (raw)
In-Reply-To: <CABXOdTckrMfM_-5+pJ37KHveLE8oRDvFAzPftnp_5--fYJVuXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
On Tue, Aug 06, 2019 at 12:58:43PM -0700, Guenter Roeck wrote:
> On Tue, Aug 6, 2019 at 12:03 PM Mark Brown <broonie@kernel.org> wrote:
> > This is the same symptoms, it will eventually time out trying to run
> > init and generate a panic. Those request_module messages are it trying
> > to load binfmt_misc which is how the kernel handles unknown binaries,
> > it's trying to run userspace but can't work out how to do that.
> Correct. Also, while there is no root file system, there is an initrd
> (or at least the log says so), and there is most likely a little
> endian binary (init ?) in that initrd.
Right, sorry - should've mentioned. You need a big endian root
filesystem (or init) to go with a big endian kernel. The kernelci one
should be:
http://storage.kernelci.org/images/rootfs/buildroot/arm64be/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-06 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 18:45 aarch64 Big Endian Nick Desaulniers
2019-08-06 19:02 ` Mark Brown
2019-08-06 19:58 ` Guenter Roeck
2019-08-06 20:08 ` Mark Brown [this message]
2019-08-06 20:45 ` Guenter Roeck
2019-08-07 12:38 ` Mark Brown
2019-08-08 21:31 ` Guillaume Tucker
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=20190806200809.GI4527@sirena.org.uk \
--to=broonie@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=groeck@google.com \
--cc=kernelci@groups.io \
--cc=ndesaulniers@google.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