All of lore.kernel.org
 help / color / mirror / Atom feed
From: Torbjorn Granlund <tg@gmplib.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Reporting Heisenbugs in qemu
Date: Tue, 07 May 2013 13:38:57 +0200	[thread overview]
Message-ID: <8661yvqasu.fsf@shell.gmplib.org> (raw)

I am trying to use qemu to

1. cover more of the assembly code in GMP
2. check configuration logic of GMP

but I am not as successful as I would like to be.

The 2nd table of http://gmplib.org/devel/testsystems.html shows all
emulated systems I am using, most of which are qemu-based.

Unfortunately, several of the qemu-based systems experience intermittent
but common segfaults:

1. Linux mips64eb 2.6.32-5-5kc-malta #1 Sun Sep 23 12:29:36 UTC 2012 mips64 GNU/Linux
2. Linux mips64el 2.6.32-5-5kc-malta #1 Fri Feb 15 21:38:11 UTC 2013 mips64 GNU/Linux
3. Linux kick.gmplib.org 2.6.18-6-sparc32 #1 Sat Dec 27 09:13:12 UTC 2008 sparc GNU/Linux

An example of a failure is:

gmp/tests/cxx/t-ops2.cc: In function 'void checkz()':
gmp/tests/cxx/t-ops2.cc:86: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>.
The bug is not reproducible, so it is likely a hardware or OS problem.

(This was from the sparc32 system.)

rootrem.c: In function 'mpn_rootrem_internal':
rootrem.c:120:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.

(From the mips64eb system.)

I am aware of that these systems don't exactly use the
kernel-of-the-week.  Newer kernels I have tried cause non-boot.  (I
don't think I've tried any newer sparc kernel, as building that would
require a stable sparc system...)

I realise that linux might have been debugged until it works on real
hardware, but that qemu might trigger untested linux execution paths.

Yesterday, I disabled GMP testing on these qemu systems, as I got tired
of the many false alarms, and since GMP looked bad.  Is there any hope
that these qemu systems will become stable?  Or aren't these problems
qemu's fault?

-- 
Torbjörn

             reply	other threads:[~2013-05-07 11:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 11:38 Torbjorn Granlund [this message]
2013-05-07 13:25 ` [Qemu-devel] Reporting Heisenbugs in qemu Mark Cave-Ayland
2013-05-07 15:50 ` Aurelien Jarno
2013-05-07 16:18   ` Torbjorn Granlund
2013-05-07 21:29 ` Artyom Tarasenko
2013-05-07 21:43   ` Torbjorn Granlund
2013-05-07 21:53     ` Artyom Tarasenko
2013-05-07 23:06       ` Torbjorn Granlund
2013-05-07 22:57   ` Aurelien Jarno
2013-05-08  7:25     ` Paolo Bonzini
2013-05-08  9:45       ` Torbjorn Granlund
2013-05-08 10:18         ` Paolo Bonzini
2013-05-09 18:15           ` Blue Swirl
2013-05-08 10:35         ` Aurelien Jarno
2013-05-09  0:28         ` Rob Landley

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=8661yvqasu.fsf@shell.gmplib.org \
    --to=tg@gmplib.org \
    --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 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.