From: Ryan Harper <ryanh@us.ibm.com>
To: xen-devel@lists.sourceforge.net
Subject: kernel BUG at arch/xen/i386/mm/hypervisor.c:99!
Date: Tue, 25 Jan 2005 14:43:48 -0600 [thread overview]
Message-ID: <20050125204348.GC8745@luffy.austin.ibm.com> (raw)
Running more SMP tests, using -unstable from 2005-01-25:
2.6.10 w/ CONFIG_SMP dom0 and multiple CONFIG_SMP domU domains (2) with
vcpus (4 and 1 respectively) and encountered this inside a domU kernel
(4 vcpus).
Failed to execute MMU updates.
------------[ cut here ]------------
kernel BUG at arch/xen/i386/mm/hypervisor.c:99!
invalid operand: 0000 [#1]
PREEMPT SMP DEBUG_PAGEALLOC
Modules linked in:
CPU: 0
EIP: 0061:[<c01157ef>]
after this, both domUs are dead, though dom0 is still alive.
Ryan Harper
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next reply other threads:[~2005-01-25 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 20:43 Ryan Harper [this message]
2005-01-25 23:57 ` kernel BUG at arch/xen/i386/mm/hypervisor.c:99! Jeff Clark
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=20050125204348.GC8745@luffy.austin.ibm.com \
--to=ryanh@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/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.