 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] (XEN) domain_crash_sync called from entry.S (ff158e99)
| To: | "Christopher S. Aker" <caker@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] (XEN) domain_crash_sync called from entry.S (ff158e99) |
| From: | Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> |
| Date: | Thu, 20 Apr 2006 08:21:41 +0100 |
| Cc: | xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Thu, 20 Apr 2006 00:26:08 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <4446F223.30002@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> <4446F223.30002@xxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 20 Apr 2006, at 03:29, Christopher S. Aker wrote: (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 00000000Do 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... Did Xen not give a call trace? Also that output doesn't indicate the reason for the crash, so there must be some bits missing from it. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] xm restore fails, Steven Hand |
|---|---|
| Next by Date: | [Xen-devel] Re: [PATCH][FIX] Possible fix for spurious interrupts, Jan Beulich |
| Previous by Thread: | Re: [Xen-devel] (XEN) domain_crash_sync called from entry.S (ff158e99), Christopher S. Aker |
| Next by Thread: | RE: [Xen-devel] (XEN) domain_crash_sync called from entry.S (ff158e99), Ian Pratt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
