qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: tg@gmplib.org (Torbjörn Granlund)
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Crashes of qemu-system-mips64 and qemu-system-mips64el
Date: Fri, 17 Oct 2014 15:53:35 +0200	[thread overview]
Message-ID: <868ukeu7j4.fsf@shell.gmplib.org> (raw)
In-Reply-To: <20141017072850.GA14823@hall.aurel32.net> (Aurelien Jarno's message of "Fri\, 17 Oct 2014 09\:28\:50 +0200")

Aurelien Jarno <aurelien@aurel32.net> writes:

  I have installation running in qemu-system-mips with weeks of uptime
  without any problem. I have however tried the above with QEMU 2.1, and
  I have been unable to reproduce the issue.
  
I have never had these problems with qemu-system-mips. They only happen
with a 64-bit kernel on qemu-system-mips64 or qemu-system-mips64el.

  It's now running for more than 48 hours, and hasn't crashed yet.
  
Which version of qemu did you use for this experiment?  Please confirm
that you used a qemu in the range I claim crashes quickly.

This crashes for me with qemu 1.7.x through 2.1.0 under GNU/Linux and
FreeBSD.  Since my reports about this issue have not until now sparked
visible activity, I haven't tested any newer qemu release.  (I have
tried every qemu release in that range but not all (qemu release) x (OS
flavour) combinations.)

(I have a mips64 and a mips64el system running under qemu 1.6.2; the
current uptime is 52 days.  These systems are used for large daily
tests, thus are quite stable.)

  Could you give us more details about your host, especially if it is a
  32-bit or a 64-bit one? Also a cat /proc/cpuinfo would be useful as some
  instructions are enabled or not depending on the host support.

All my hosts are 64-bit x86.

I don't have the broken stuff set up any longer (2.5 month later) but
since my many attempts over the years trying to get a qemu post 1.6.x to
work I on many different pieces of hardware, the exact x86 hardware is
almost certainly irrelevant.  My hardware platforms are quite diverse.

-- 
Torbjörn
Please encrypt, key id 0xC8601622

  reply	other threads:[~2014-10-17 13:53 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 [this message]
2014-10-17 18:23     ` Aurelien Jarno
2014-10-17 18:57       ` Torbjörn Granlund
2014-10-17 19:09         ` Aurelien Jarno
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=868ukeu7j4.fsf@shell.gmplib.org \
    --to=tg@gmplib.org \
    --cc=aurelien@aurel32.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).