qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] i586 TCG: boot hangs intermittently on cryptomgr_test at doublefault_fn
Date: Tue, 2 Jun 2009 18:58:33 +0100	[thread overview]
Message-ID: <20090602175833.GA26882@amd.home.annexia.org> (raw)


I have this bug[1] apparently in qemu which I'm trying to track down:

----------------------------------------------------------------------
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
audit: initializing netlink socket (disabled)
type=2000 audit(1243614582.002:1): initialized
HugeTLB registered 4 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 680
BUG: unable to handle kernel NULL pointer dereference at 00000014
IP: [<c041ddd9>] doublefault_fn+0xd/0x108
*pde = 00000000 
Oops: 0000 [#1] SMP 
last sysfs file: 
Modules linked in:

Pid: 26, comm: cryptomgr_test Not tainted (2.6.30-0.91.rc7.git1.fc12.i586 #1) 
EIP: 0060:[<c041ddd9>] EFLAGS: f8d8409e CPU: 0
EIP is at doublefault_fn+0xd/0x108
EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000
ESI: 00000000 EDI: 00000000 EBP: c0be1e2c ESP: c0be1e18
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process cryptomgr_test (pid: 26, ti=c0be0000 task=d5418000 task.ti=d5b88000)
Stack:
 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Call Trace:
Code: c2 eb 00 ba b8 dd 41 c0 ff e2 8d 15 e4 61 99 c0 8b 0a 51 8d 15 e0 61 99
c0 8b 0a 51 c3 90 55 89 e5 56 53 83 ec 0c 0f 1f 44 00 00 <65> a1 14 00 00 00 89
45 f4 31 c0 8d 45 ee 66 c7 45 ee 00 00 c7 
EIP: [<c041ddd9>] doublefault_fn+0xd/0x108 SS:ESP 0068:c0be1e18
CR2: 0000000000000014
---[ end trace 6d450e935ee1897c ]---
cryptomgr_test used greatest stack depth: 7348 bytes left
----------------------------------------------------------------------

It seems to be: i386 architecture only, software emulation, and
intermittent, quite hard to reproduce reliably.

So my questions are: Has anyone seen anything like this before?
Is there anything I can set or enable to track down which instructions
are failing?

Rich.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=503236

-- 
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top

             reply	other threads:[~2009-06-02 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 17:58 Richard W.M. Jones [this message]
2009-06-02 18:15 ` [Qemu-devel] i586 TCG: boot hangs intermittently on cryptomgr_test at doublefault_fn Paul Brook
2009-06-02 18:59 ` malc
2009-06-02 19:10   ` Avi Kivity
2009-06-02 19:08 ` Avi Kivity
2009-06-02 20:43   ` [Qemu-devel] " Jan Kiszka

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=20090602175833.GA26882@amd.home.annexia.org \
    --to=rjones@redhat.com \
    --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).