[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Crashes of qemu-system-mips64 and qemu-system-mips64el
From: |
Aurelien Jarno |
Subject: |
Re: [Qemu-devel] Crashes of qemu-system-mips64 and qemu-system-mips64el |
Date: |
Fri, 17 Oct 2014 21:09:20 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Oct 17, 2014 at 08:57:38PM +0200, Torbjörn Granlund wrote:
> Aurelien Jarno <address@hidden> 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
address@hidden http://www.aurel32.net