All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>,
	Romain Naour <romain.naour@smile.fr>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Weird issue with uClibc RISC-V 32-bit in Qemu
Date: Sun, 28 Jul 2024 19:01:15 +0200	[thread overview]
Message-ID: <20240728190115.2e9fc088@windsurf> (raw)

Hello,

I am working on updating the toolchains of toolchains.bootlin.com, and
as part of that rebuilding all toolchains with Buildroot 2024.05 + a
few patches:

  https://github.com/bootlin/buildroot-toolchains/tree/toolchains.bootlin.com-2024.05

On riscv32-ilp32d, I have the uClibc stable toolchain that generates a
system that doesn't boot under Qemu: the kernel boots fine, but when
switching to user-space, nothing happens:

  https://gitlab.com/buildroot.org/toolchains-builder/-/jobs/7378190992

The interesting thing is that the uClibc bleeding-edge toolchain works
fine. The only difference is that GCC is 14.x instead of 13.x, and
binutils is 2.42 instead of 2.41. Bleeding edge toolchain:

  https://gitlab.com/buildroot.org/toolchains-builder/-/jobs/7378190991

I took just the rootfs.ext2 of the "working" build, and put it together
with the firmware+kernel of the "non working" build, and it works fine:
so the problem is in the rootfs.

In the broken build, if I pass init=/bin/sh, then I'm dropped into a
shell, but some things are weird:

 - When I run ls, the first line of output starts right after the
   prompt, not in a newline

 - After ls has finished, it doesn't got back to the shell prompt,
   unless I press Enter again

Using init=/bin/sh with the fully working rootfs does not exhibit this
issue.

You can retrieve the non-working artefacts and defconfig at:

  https://gitlab.com/buildroot.org/toolchains-builder/-/jobs/7378190992/artifacts/browse/test/output/

And the working artefact and defconfig at:

  https://gitlab.com/buildroot.org/toolchains-builder/-/jobs/7378190991/artifacts/browse/test/output/

Do you have any clue at what could be happening here?

Thanks for your support!

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

             reply	other threads:[~2024-07-28 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 17:01 Thomas Petazzoni via buildroot [this message]
2024-07-30  4:06 ` [Buildroot] Weird issue with uClibc RISC-V 32-bit in Qemu Waldemar Brodkorb
2024-07-30  4:18 ` Waldemar Brodkorb

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=20240728190115.2e9fc088@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@openadk.org \
    /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.