From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Max Filippov <jcmvbkbc@gmail.com>,
Romain Naour <romain.naour@smile.fr>,
Niklas Cassel <niklas.cassel@wdc.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Xtensa qemu nommu defconfig not working
Date: Fri, 25 Nov 2022 19:11:55 +0100 [thread overview]
Message-ID: <20221125191155.111c4ddc@windsurf> (raw)
Hello,
The configs/qemu_xtensa_lx60_nommu_defconfig builds correctly, but
fails to boot under Qemu:
[ 1.158675] Freeing unused kernel image (initmem) memory: 460K
[ 1.159475] This architecture does not have kernel memory protection.
[ 1.160806] Run /init as init process
[ 1.186746] binfmt_flat: reloc outside program 0x24c80100 (0 - 0x6e430/0x56a20), killing init!
[ 1.190881] Failed to execute /init (error -8)
[ 1.191529] Run /sbin/init as init process
[ 1.204778] binfmt_flat: reloc outside program 0x24c80100 (0 - 0x6e430/0x56a20), killing init!
[ 1.206216] Starting init: /sbin/init exists but couldn't execute it (error -8)
[ 1.207229] Run /etc/init as init process
[ 1.209332] Run /bin/init as init process
[ 1.210517] Run /bin/sh as init process
[ 1.220290] binfmt_flat: reloc outside program 0x24c80100 (0 - 0x6e430/0x56a20), killing sh!
[ 1.221658] Starting init: /bin/sh exists but couldn't execute it (error -8)
[ 1.223403] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[ 1.226218] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. ]---
There were some changes in elf2flt:
9dd179d43ffe9be98035f921a0db2bf051b632fb package/elf2flt: fix fatal error regression on m68k, xtensa, riscv64
95402089c314fbc03b934f5fcf9c29db043d758c package/elf2flt: remove broken patch
b07210b272c6e8810b038190cf5c1fd1f7b48397 package/gcc: remove BR2_GCC_ENABLE_LTO
9db5eb258cf492567bac33a33cb606f14045639d package/elf2flt: Remove Config.in.host
3e50b5fe2632a3081fd3f6574a5e9525fa897fdb package/elf2flt: update AUTORECONF comment
32f93b0ef2c602dfa1f5b243ba865d5b16e2fa33 package/elf2flt: update RISC-V 64-bits support
65d78dcfeb8b2eafaebe2d0c3c8c42e7e85f46ac package/elf2flt: update to version 2021.08
6d49446ebdbd32c1b4591c0aa8cacb189a69e318 package/elf2flt: add RISC-V 64-bits support
However, in commit 9dd179d43ffe9be98035f921a0db2bf051b632fb, Niklas
said about the qemu_xtensa_lx60_nommu_defconfig configuration: "xtensa
crashes when loading init, the same behavior as when reverting the bad
upstream elf2flt commit completely."
Max, do you think you could have a look at what is happening?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-11-25 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 18:11 Thomas Petazzoni via buildroot [this message]
2022-11-28 11:54 ` [Buildroot] Xtensa qemu nommu defconfig not working Max Filippov
2022-11-28 13:12 ` Thomas Petazzoni via buildroot
2022-11-28 13:37 ` Max Filippov
2022-12-27 13:53 ` Thomas Petazzoni via buildroot
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=20221125191155.111c4ddc@windsurf \
--to=buildroot@buildroot.org \
--cc=jcmvbkbc@gmail.com \
--cc=niklas.cassel@wdc.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.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