From: LIU Zhiwei <baxiantai@gmail.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>
Subject: Re: qemu-riscv32 usermode still broken?
Date: Wed, 13 Sep 2023 09:41:39 +0800 [thread overview]
Message-ID: <15820654-5d7f-fd66-3d34-da1a55d2a53e@gmail.com> (raw)
In-Reply-To: <10817413.NyiUUSuA9g@pinacolada>
On 2023/9/13 6:31, Andreas K. Huettel wrote:
> Dear all,
>
> I've once more tried to build up a riscv32 linux install in a qemu-riscv32
> usermode systemd-nspawn, and am running into the same problems as some time
> ago...
>
> https://dev.gentoo.org/~dilfridge/riscv32/riscv32.tar.xz (220M)
>
> The problems manifest themselves mostly in bash; if I replace /bin/bash
> with a static x86-64 binary (in the tarball as /bin/bash.amd64), bypassing
> qemu, I can make the chroot rebuild itself completely.
>
> https://lists.gnu.org/archive/html/bug-bash/2023-09/msg00119.html
> ^ Here I'm trying to find out more.
>
> Bash tests apparently indicate that argv[0] is overwritten, and that
> reading through a pipe or from /dev/tty fails or loses data.
>
> Apart from the bash testsuite failing, symptoms are as follows:
>
> * Something seems wrong in the signal handling (?):
If it is wrong for signal handling and for 32-bit, I guess it may be
fixed by this patch
https://www.mail-archive.com/qemu-devel@nongnu.org/msg981238.html
And this patch has been merged into master branch yesterday.
May be you can have a try based on the master branch.
Thanks,
Zhiwei
> --- our package manager (bash/python combo, there bash) hangs reproducibly at
> one point.
> --- when I run a console program and try to background it with ctl-z, it hangs
> (only the first time per bash instance, it seems)
> repeated ctl-c gets me back to the shell, then the program is in the
> background
>
> riscv32 ~ # python
> Python 3.11.5 (main, Aug 31 2023, 21:56:30) [GCC 13.2.1 20230826] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> [1]+ Stopped python
> ^C^C^C^C^C^C^C
> riscv32 ~ # ^C
> riscv32 ~ #
> riscv32 ~ # jobs
> [1]+ Stopped python
> riscv32 ~ # fg
> python
>
>
> --- make, when building something, seems to always start only one job in
> parallel
>
> Any advice or debugging would be appreciated.
>
> If we get this running then I can set up regular riscv32 Gentoo stage builds
> within a week. [*]
>
> Thanks in advance,
> Andreas
>
> PS.
> huettel@pinacolada ~ $ /var/lib/machines/riscv32/usr/bin/qemu-riscv32 -version
> qemu-riscv32 version 8.1.0
> Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
>
>
> [*] https://www.gentoo.org/downloads/#riscv
>
next prev parent reply other threads:[~2023-09-13 1:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 22:31 qemu-riscv32 usermode still broken? Andreas K. Huettel
2023-09-13 1:41 ` LIU Zhiwei [this message]
2023-09-13 8:06 ` Michael Tokarev
2023-09-13 10:33 ` Andreas K. Huettel
2023-09-14 1:22 ` Andreas K. Huettel
2023-09-16 22:37 ` Andreas K. Huettel
2023-09-18 1:16 ` Alistair Francis
2023-09-19 20:39 ` Andreas K. Huettel
2024-06-11 4:43 ` Alistair Francis
2024-06-11 8:57 ` Andreas K. Huettel
2024-06-12 1:26 ` Alistair Francis
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=15820654-5d7f-fd66-3d34-da1a55d2a53e@gmail.com \
--to=baxiantai@gmail.com \
--cc=dilfridge@gentoo.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).