From: "Christopher S. Aker" <caker@theshore.net>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: (XEN) domain_crash_sync called from entry.S (ff158e99)
Date: Wed, 19 Apr 2006 21:29:55 -0500 [thread overview]
Message-ID: <4446F223.30002@theshore.net> (raw)
In-Reply-To: <443C06DD.4050506@theshore.net>
Another ... this time with Xen 3.0.2-2.
(XEN) domain_crash_sync called from entry.S (ff157585)
(XEN) Domain 32 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0.2-2 Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: 0061:[<c0101347>]
(XEN) EFLAGS: 00010a17 CONTEXT: guest
(XEN) eax: 00000000 ebx: c4a69e54 ecx: 00000001 edx: 00000000
(XEN) esi: 00007ff0 edi: c3d9f550 ebp: c4a69e80 esp: c4a69e00
(XEN) cr0: 8005003b cr3: 7fe2d000
(XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0069 cs: 0061
(XEN) Guest stack trace from esp=c4a69e00:
(XEN) Fault while accessing guest memory.
(XEN) ----[ Xen-3.0.2-2 Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: e008:[<ff11f593>] put_page_type+0x13/0xa0
(XEN) EFLAGS: 00210296 CONTEXT: hypervisor
(XEN) eax: f6800000 ebx: feca7038 ecx: 001fc94c edx: f6157242
(XEN) esi: a72b9210 edi: a72b9210 ebp: f97adf20 esp: ff23dce4
(XEN) cr0: 80050033 cr3: 7ffda000
(XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from esp=ff23dce4:
(XEN) ffbdf080 ffbf6480 00000001 ff157149 feca7038 a72b9210 001fc94c
ff11f795
(XEN) a72b9210 001aed41 ffbf6514 ff23dfb4 00000000 feca7038 00000007
ff11f360
(XEN) 001fc94c ff11d6b3 ff11b5e6 ff23dd34 ff23dfb4 ffbe6000 feca7000
40030001
(XEN) 40030000 f97adf20 fec9d000 ff11f616 f97adf20 50030001 00000001
ff157149
(XEN) fec9d020 f97adf20 0007fe2d ff11f715 f97adf20 ff23ddb8 ffbf6514
ff23dfb4
(XEN) 00000000 fec9d020 00000004 ff11f3cd 0007fe2d f93a7228 f871c340
ff1254e7
(XEN) 7ffda000 ffbe6000 ffbe6498 60000001 60000000 f73fd438 f73fd438
ff11f616
(XEN) f73fd438 70000001 f871c340 00000002 80000003 ffa58080 f73fd438
ff118718
(XEN) f73fd438 00000000 ffa58080 ff118959 80000003 ffa58080 ffa58090
00000000
Do you think this, and my other issue could be faulty memory? I ran
memtest86 for 24+ hours before I deployed this box, but you never know...
-Chris
next prev parent reply other threads:[~2006-04-20 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 19:43 (XEN) domain_crash_sync called from entry.S (ff158e99) Christopher S. Aker
2006-04-20 2:29 ` Christopher S. Aker [this message]
2006-04-20 7:21 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-04-13 0:43 Ian Pratt
2006-04-13 1:31 ` Nivedita Singhvi
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=4446F223.30002@theshore.net \
--to=caker@theshore.net \
--cc=xen-devel@lists.xensource.com \
/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.