From: Laurent Vivier <laurent@vivier.eu>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Artyom Tarasenko" <atar4qemu@gmail.com>,
"Richard Henderson" <rth@twiddle.net>
Cc: "Fam Zheng" <famz@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] sparc64 linux-user status
Date: Thu, 25 May 2017 09:56:25 +0200 [thread overview]
Message-ID: <54ce558d-3571-fb30-db3f-59b58ec979fc@vivier.eu> (raw)
In-Reply-To: <87h90d3sz9.fsf@linaro.org>
Le 22/05/2017 à 15:45, Alex Bennée a écrit :
> Hi,
>
> While looking at some of the docker cross-build patches I thought I'd
> checkout if I could still bootstrap some Debian linux-user images. I
> made some tweaks to allow debootstrap to bootstrap from Debian's ports
> to see if I could get the SPARC64 file-system up and running:
>
> https://github.com/stsquad/qemu/commits/docker/sparc64-linux-user
I was waiting that for a while, thanks!
>
> However when I try to run it:
>
> make docker-image-debian-sparc64-user V=1
>
> It fails:
>
> Step 4 : RUN /debootstrap/debootstrap --second-stage
> ---> Running in 2241c809c19f
> *** longjmp causes uninitialized stack frame ***: /bin/sh terminated
> Illegal instruction (core dumped)
> *** longjmp causes uninitialized stack frame ***: /bin/sh terminated
> Illegal instruction (core dumped)
> *** longjmp causes uninitialized stack frame ***: /bin/sh terminated
> Illegal instruction (core dumped)
> I: Keyring file not available at /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror https://deb.debian.org/debian
> W: Failure trying to run: dpkg-deb -f /var/cache/apt/archives/dpkg_1.18.24_sparc64.deb Version
> W: See //debootstrap/debootstrap.log for details
> I: Installing core packages...
> W: Failure trying to run: dpkg --force-depends --install /var/cache/apt/archives/base-passwd_3.5.43_sparc64.deb
> W: See //debootstrap/debootstrap.log for details
> Illegal instruction (core dumped)
> The command '/bin/sh -c /debootstrap/debootstrap --second-stage' returned a non-zero code: 132
>
> Although I can manually get the shell at least partially running:
>
> 14:43 last:125, alex@zen taken:25, git:docker/sparc64-linux-user, [/home/alex/lsrc/qemu/qemu.git]> docker run --rm -it 1084ed198b00 /bin/sh
> # uname -a
> [1] + Stopped (tty output) uname -a
> # uname -a | cat
> [2] + Stopped (tty output) uname -a | cat
> # echo "hello"
> hello
> #
>
> Bringing anything to the foreground hangs the window:
>
> # fg
> uname -a | cat
> Linux 8cbf3e5e2234 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 sun4u GNU/Linux
> /bin/sh: 4: fg: Cannot set tty process group (Inappropriate ioctl for device)
> *** longjmp causes uninitialized stack frame ***: /bin/sh terminated
>
> Which makes me think it might be a linux-user bug rather than the main
> translation. Is this a tested combination? Any idea what the bug could be?
Do you know if the default CPU for linux-user is the good one for
debian-sparc64?
I used to run linux-user in a container, and I have this kind of problem
too. The last time I have checked I think it was because a floating
point instruction emulation failure. I don't know how works sparc64, but
on some architectures, FPU instructions are emulated by the kernel, so
it could explain why it works in softmmu mode and not in linux-user
mode: qemu doesn't emulate it because it relies on the kernel for that,
and in this case the kernel can't.
Laurent
next prev parent reply other threads:[~2017-05-25 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 13:45 [Qemu-devel] sparc64 linux-user status Alex Bennée
2017-05-25 7:43 ` Mark Cave-Ayland
2017-05-30 10:04 ` Alex Bennée
2017-05-25 7:56 ` Laurent Vivier [this message]
2017-05-30 9:49 ` Artyom Tarasenko
2017-05-30 10:40 ` Peter Maydell
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=54ce558d-3571-fb30-db3f-59b58ec979fc@vivier.eu \
--to=laurent@vivier.eu \
--cc=alex.bennee@linaro.org \
--cc=atar4qemu@gmail.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).