From: Aurelien Jarno <aurelien@aurel32.net>
To: "Torbjörn Granlund" <tg@gmplib.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Crashes of qemu-system-mips64 and qemu-system-mips64el
Date: Fri, 17 Oct 2014 21:09:20 +0200 [thread overview]
Message-ID: <20141017190920.GC14823@hall.aurel32.net> (raw)
In-Reply-To: <86h9z25xst.fsf@shell.gmplib.org>
On Fri, Oct 17, 2014 at 08:57:38PM +0200, Torbjörn Granlund wrote:
> Aurelien Jarno <aurelien@aurel32.net> writes:
>
> I am using 2.1.2 under GNU/Linux.
>
> Ah, so you're not trying to reproduce the problem!
I do. Well you talked about 2.1.0, the latest stable one is 2.1.2. Now
if you prefer, we can conclude the problem is solved in 2.1.2.
> Are you passing the -cpu 5Kc argument?
I used:
qemu-system-mips64 -M malta -cpu 5Kc -m 256 \
-drive file=disk.img,if=virtio,index=0 \
-net nic,macaddr=52:54:00:13:06:64 -net user,hostfwd=tcp::20008-:22 \
-kernel boot/vmlinux-3.2.0-4-5kc-malta \
-initrd boot/initrd.img-3.2.0-4-5kc-malta \
-append "root=/dev/vda1 console=ttyS0" \
-nographic -serial null -monitor null
And it's still running the testsuite in a loop.
> I don't think it's irrelevant, that's why I asked. If you don't provide
> this information, we won't be able to check which code paths are
> involved
>
> Given you are the only one to reproduce the issue, please provide a
> backtrace of a crash so that we can proceed further.
>
> Really? Has anybody tried to reproduce the issue?
At least me, and it doesn't crash here.
> My bug report contains all information for trivially reproducing the
> issue. I kept the setup around for a long time, but now I have cleaned
Yes, but it doesn't mean it's reproducible.
> it up. I am very busy in this period and cannot afford to set it up
> again, also considering that the effort on the developer part seems very
> very limited wrt reported problems. (I am not complaining, I have no
> opinion on how volunteer hackers use their time!)
Ok fine, let's consider the issue fixed.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2014-10-17 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 20:49 [Qemu-devel] Crashes of qemu-system-mips64 and qemu-system-mips64el Torbjörn Granlund
2014-08-03 0:11 ` Torbjörn Granlund
2014-10-17 7:32 ` Aurelien Jarno
2014-10-17 7:28 ` Aurelien Jarno
2014-10-17 13:53 ` Torbjörn Granlund
2014-10-17 18:23 ` Aurelien Jarno
2014-10-17 18:57 ` Torbjörn Granlund
2014-10-17 19:09 ` Aurelien Jarno [this message]
2014-10-22 20:31 ` Torbjörn Granlund
2014-10-22 22:07 ` Aurelien Jarno
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=20141017190920.GC14823@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=tg@gmplib.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.