From: Laurent Vivier <laurent@vivier.eu>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Cc: Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Kernel crash on qemu-m68k-system while building r-cran packages
Date: Sat, 30 May 2020 17:12:16 +0200 [thread overview]
Message-ID: <1856e243-11fd-e03a-ee90-23167b90f46d@vivier.eu> (raw)
In-Reply-To: <b13f2500-0c31-1e6f-19f2-f04ea58edde3@physik.fu-berlin.de>
Le 30/05/2020 à 13:49, John Paul Adrian Glaubitz a écrit :
> Hi Michael!
>
> On 5/30/20 1:49 AM, Michael Schmitz wrote:
>> Can you try to run that R binary on a real 060 or 040?
> Works fine on elgar:
>
> root@elgar:~> R
As the package is available, I've been able to reproduce the problem
with logs enabled. Apparently the instruction is not decoded correctly:
----------------
IN:
0x00016a2c: fmovel #0,%fpsr
Disassembler disagrees with translator over instruction decoding
Please report this to qemu-devel@nongnu.org
OP:
ld_i32 tmp0,env,$0xfffffffffffffff0
movi_i32 tmp1,$0x0
brcond_i32 tmp0,tmp1,lt,$L0
---- 00016a2c 00000000
movi_i32 PC,$0x16a2c
movi_i32 tmp0,$0x3
call raise_exception,$0x0,$0,env,tmp0
set_label $L0
exit_tb $0x7fc2a0da5643
INT 49331: Address Error(0xc) pc=00016a2c sp=3cc91f30 sr=2004
I try to fix that...
Thanks,
Laurent
next prev parent reply other threads:[~2020-05-30 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 9:14 Kernel crash on qemu-m68k-system while building r-cran packages John Paul Adrian Glaubitz
2020-05-27 9:25 ` John Paul Adrian Glaubitz
2020-05-29 23:49 ` Michael Schmitz
2020-05-30 8:58 ` Laurent Vivier
2020-05-30 11:49 ` John Paul Adrian Glaubitz
2020-05-30 15:12 ` Laurent Vivier [this message]
2020-05-30 15:27 ` John Paul Adrian Glaubitz
2020-05-30 16:19 ` Laurent Vivier
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=1856e243-11fd-e03a-ee90-23167b90f46d@vivier.eu \
--to=laurent@vivier.eu \
--cc=debian-68k@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.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;
as well as URLs for NNTP newsgroup(s).