[Xen-bugs] [Bug 128] x86_64 - Dom0 crashed while running LTP on DomU

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=128





------- Additional Comments From dbarrera@xxxxxxxxxx  2005-07-29 19:31 -------
I rebooted Dom0 and DomU and restarted LTP on both domains. LPT was running on
DomU and compiling (not yet running) on Dom0 when the machine spontaneously
rebooted; I don't know if this is a separate problem, but for now I am lumping
them together. Here's the trace from the spontaneous reboot:

Welcome to SUSE LINUX Enterprise Server 9 (x86_64) - Kernel 2.6.12-xen0 (ttyS0).


(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU:    0
(XEN) EIP:    e030:[<ffffffff802be207>] ???
(XEN) EFLAGS: 0000000000010207
(XEN) rax: 0000000000000000   rbx: ffff88000cba4c18   rcx: ffffffffff577000  
rdx: ffffffff8047fe60
(XEN) rsi: ffffffff80536780   rdi: ffff88000cba4b60   rbp: ffffffff804f2a10  
rsp: ffff880001b7ce78
(XEN) r8:  0000000000000007   r9:  0000000000000007   r10: 00000000000002a0  
r11: 000000000000001c
(XEN) r12: ffff88000cba4b60   r13: ffff88000cba4b60   r14: ffff880001b7ff58  
r15: ffff880001b7e678
(XEN) Xen stack trace from rsp=ffff880001b7ce78:
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 000000000H   
\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffffB90000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
000000000000000\uffff\uffffB900000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) Xen call trace from rsp=ffff880001b7ce78:
(XEN)    Trace empty.
(XEN) Domain 0 shutdown: rebooting machine.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs