From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1344320 <1344320@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1344320] [NEW] qemu-aarch64 cannot execute glibc
Date: Sat, 19 Jul 2014 11:54:24 +0100 [thread overview]
Message-ID: <CAFEAcA-hfcHW0Fpxut+AsSoTgd38nsRBf39Xym9gYJ6GHBESwg@mail.gmail.com> (raw)
In-Reply-To: <20140718203004.20624.43575.malonedeb@wampee.canonical.com>
On 18 July 2014 21:30, Andreas Schwab <schwab@linux-m68k.org> wrote:
> qemu: uncaught target signal 4 (Illegal instruction) - core dumped
> Illegal instruction
> $ objdump -d /daten/build/build-root/home/abuild/rpmbuild/BUILD/glibc-2.19.90/cc-base/elf/ld-linux-aarch64.so.1 | grep ' 4828:'
> 4828: d53be040 mrs x0, cntvct_el0
That's awkward, it looks like glibc has started reading the
generic timer from userspace, and our implementation is
#ifndef CONFIG_USER_ONLY.
Do we have any current implementations of timers/counters
used by linux-user?
thanks
-- PMM
next prev parent reply other threads:[~2014-07-19 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 20:30 [Qemu-devel] [Bug 1344320] [NEW] qemu-aarch64 cannot execute glibc Andreas Schwab
2014-07-19 10:54 ` Peter Maydell [this message]
2014-07-21 18:55 ` Richard Henderson
2014-07-21 10:46 ` [Qemu-devel] [Bug 1344320] " Peter Maydell
2014-07-21 19:00 ` Richard Henderson
2014-07-21 20:37 ` Peter Maydell
2014-07-22 19:46 ` Richard Henderson
2014-07-22 22:22 ` Peter Maydell
2014-07-24 21:45 ` Richard Henderson
2014-07-25 8:54 ` Riku Voipio
2014-07-25 9:02 ` Ard Biesheuvel
2014-07-21 10:56 ` Peter Maydell
2014-08-29 11:48 ` 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=CAFEAcA-hfcHW0Fpxut+AsSoTgd38nsRBf39Xym9gYJ6GHBESwg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=1344320@bugs.launchpad.net \
--cc=qemu-devel@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).