Hi, Buildroot and OpenADK have samples to create a Linux system to be bootup in Qemu system emulation for microblaze architecture. With gcc 6.3 and 7.1 the samples are not working anymore, because the Linux system userland does not boot. Qemu 2.9.0: Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b (with glibc, musl and uClibc-ng toolchains) I bisected gcc source code and found the bad commit: 6dcad60c0ef48af584395a40feeb256fb82986a8 When reverting the change, gcc 6.3 and 7.1 produces working Linux rootfs again. What can we do about it? best regards Waldemar
Hello, On Sat, 27 May 2017 10:51:22 +0200, Waldemar Brodkorb wrote:
Buildroot and OpenADK have samples to create a Linux system to be bootup in Qemu system emulation for microblaze architecture.
With gcc 6.3 and 7.1 the samples are not working anymore, because the Linux system userland does not boot. Qemu 2.9.0: Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b (with glibc, musl and uClibc-ng toolchains)
I bisected gcc source code and found the bad commit: 6dcad60c0ef48af584395a40feeb256fb82986a8
Nice, great work!
When reverting the change, gcc 6.3 and 7.1 produces working Linux rootfs again.
What can we do about it?
1. Add a revert of this commit in Buildroot for gcc 6.x and 7.x 2. Report the bug upstream, pointing to the problematic commit Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
On 05/27/2017 01:51 AM, Waldemar Brodkorb wrote:
Hi,
Buildroot and OpenADK have samples to create a Linux system to be bootup in Qemu system emulation for microblaze architecture.
With gcc 6.3 and 7.1 the samples are not working anymore, because the Linux system userland does not boot. Qemu 2.9.0: Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b (with glibc, musl and uClibc-ng toolchains)
I bisected gcc source code and found the bad commit: 6dcad60c0ef48af584395a40feeb256fb82986a8
When reverting the change, gcc 6.3 and 7.1 produces working Linux rootfs again.
What can we do about it?
I will revert this commit in GCC. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
On 05/27/2017 09:09 AM, Michael Eager wrote:
On 05/27/2017 01:51 AM, Waldemar Brodkorb wrote:
Hi,
Buildroot and OpenADK have samples to create a Linux system to be bootup in Qemu system emulation for microblaze architecture.
With gcc 6.3 and 7.1 the samples are not working anymore, because the Linux system userland does not boot. Qemu 2.9.0: Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b (with glibc, musl and uClibc-ng toolchains)
I bisected gcc source code and found the bad commit: 6dcad60c0ef48af584395a40feeb256fb82986a8
When reverting the change, gcc 6.3 and 7.1 produces working Linux rootfs again.
What can we do about it?
I will revert this commit in GCC.
Reverted on GCC mainline: Committed revision 248540. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
On 05/27/2017 06:09 PM, Michael Eager wrote:
On 05/27/2017 01:51 AM, Waldemar Brodkorb wrote:
Hi,
Buildroot and OpenADK have samples to create a Linux system to be bootup in Qemu system emulation for microblaze architecture.
With gcc 6.3 and 7.1 the samples are not working anymore, because the Linux system userland does not boot. Qemu 2.9.0: Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b (with glibc, musl and uClibc-ng toolchains)
I bisected gcc source code and found the bad commit: 6dcad60c0ef48af584395a40feeb256fb82986a8
When reverting the change, gcc 6.3 and 7.1 produces working Linux rootfs again.
What can we do about it?
I will revert this commit in GCC.
Hi. Looks the revert caused: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485 Thanks, Martin
participants (4)
-
Martin Liška -
Michael Eager -
Thomas Petazzoni -
Waldemar Brodkorb