From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47775)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tg@gmplib.org>) id 1XfCig-00059Z-F5
	for qemu-devel@nongnu.org; Fri, 17 Oct 2014 14:57:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tg@gmplib.org>) id 1XfCia-0003cn-Aj
	for qemu-devel@nongnu.org; Fri, 17 Oct 2014 14:57:46 -0400
Received: from servus.gmplib.org ([193.10.5.126]:57871 helo=shell.gmplib.org)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tg@gmplib.org>) id 1XfCia-0003a2-41
	for qemu-devel@nongnu.org; Fri, 17 Oct 2014 14:57:40 -0400
References: <86egwyfwh9.fsf@shell.gmplib.org>
	<20141017072850.GA14823@hall.aurel32.net>
	<868ukeu7j4.fsf@shell.gmplib.org>
	<20141017182324.GW24004@hall.aurel32.net>
From: tg@gmplib.org (=?utf-8?Q?Torbj=C3=B6rn?= Granlund)
Sender: tg@gmplib.org
Date: Fri, 17 Oct 2014 20:57:38 +0200
In-Reply-To: <20141017182324.GW24004@hall.aurel32.net> (Aurelien Jarno's
	message of "Fri\, 17 Oct 2014 20\:23\:24 +0200")
Message-ID: <86h9z25xst.fsf@shell.gmplib.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Crashes of qemu-system-mips64 and
	qemu-system-mips64el
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org

Aurelien Jarno <aurelien@aurel32.net> writes:
=20=20
  I am using 2.1.2 under GNU/Linux.
=20=20
Ah, so you're not trying to reproduce the problem!

Are you passing the -cpu 5Kc argument?

  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
=20=20
  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?

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
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!)

--=20
Torbj=C3=B6rn
Please encrypt, key id 0xC8601622