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

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

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 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...
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