From: Nick Desaulniers <ndesaulniers@google.com>
To: egorenar@linux.ibm.com, Vasily Gorbik <gor@linux.ibm.com>
Cc: Joel Stanley <joel@jms.id.au>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Guenter Roeck <linux@roeck-us.net>,
Nathan Chancellor <natechancellor@gmail.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: s390 - buildroot + qemu
Date: Fri, 16 Oct 2020 16:11:11 -0700 [thread overview]
Message-ID: <CAKwvOd=0nOhK4KoLb1_Jni5u3ENDx10QeAxfYcSbtFQs77FxAw@mail.gmail.com> (raw)
Hello all,
I'm working on integrating the latest release of buildroot (2020.08.1)
into our CI for ClangBuiltLinux.
https://github.com/ClangBuiltLinux/boot-utils/pull/25
https://github.com/ClangBuiltLinux/boot-utils/pull/26
https://github.com/ClangBuiltLinux/continuous-integration/pull/327
I'm seeing the following error from QEMU:
KASLR disabled: CPU has no PRNG
Linux version 5.9.0-00732-g04ed4527465f (ndesaulniers@<myhost>) #30
SMP Fri Oct 16 15:49:05 PDT 2020Kernel fault: interruption code 0005
ilc:2
PSW : 0000200180000000 000000000001779e
R:0 T:0 IO:0 EX:0 Key:0 M:0 W:0 P:0 AS:0 CC:2 PM:0 RI:0 EA:3
GPRS: 0000000000000001 0000000c00000000 00000003fffffff4 00000000fffffff0
0000000000000000 00000000fffffff4 000000000000000c 00000000fffffff0
00000000fffffffc 0000000000000000 00000000fffffff8 00000000008a75a8
0000000000000009 0000000000000002 0000000000000008 000000000000bce0
This is via a kernel built by:
$ ARCH=s390 CROSS_COMPILE=s390x-linux-gnu- make CC=clang -j71 defconfig
$ ARCH=s390 CROSS_COMPILE=s390x-linux-gnu- make CC=clang -j71
The booting qemu:
$ qemu-system-s390x -M s390-ccw-virtio -append 'rdinit=/bin/sh '
-display none -initrd /android1/boot-utils/images/s390/rootfs.cpio
-kernel /android0/kernel-all/arch/s390/boot/bzImage -m 512m
-nodefaults -serial mon:stdio
Is there a preferred kernel config or additional flags to QEMU I
should be using to avoid this error? It's also possible that there's
a bug in the kernel image, but given that it fails very early with no
other output, I am slightly suspicious of that.
--
Thanks,
~Nick Desaulniers
next reply other threads:[~2020-10-16 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 23:11 Nick Desaulniers [this message]
2020-10-16 23:18 ` s390 - buildroot + qemu Guenter Roeck
2020-10-16 23:40 ` Nick Desaulniers
2020-10-17 0:15 ` Guenter Roeck
2020-10-19 10:54 ` Christian Borntraeger
2020-10-19 14:51 ` Guenter Roeck
2020-10-19 21:36 ` Nick Desaulniers
2020-10-19 22:03 ` Guenter Roeck
2020-10-20 5:34 ` Christian Borntraeger
2020-10-19 11:44 ` Cornelia Huck
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='CAKwvOd=0nOhK4KoLb1_Jni5u3ENDx10QeAxfYcSbtFQs77FxAw@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=egorenar@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-s390@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=natechancellor@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.