This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] (XEN) domain_crash_sync called from entry.S (ff158e99)

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] (XEN) domain_crash_sync called from entry.S (ff158e99)
From: "Christopher S. Aker" <caker@xxxxxxxxxxxx>
Date: Wed, 19 Apr 2006 21:29:55 -0500
Delivery-date: Wed, 19 Apr 2006 19:30:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <443C06DD.4050506@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <443C06DD.4050506@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Windows/20051201)
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...


Xen-devel mailing list