WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 127] x86_64 - Dom0 crashes when copying a file over NFS

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 127] x86_64 - Dom0 crashes when copying a file over NFS from DomU to an NFS share
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 29 Jul 2005 18:34:13 +0000
Delivery-date: Fri, 29 Jul 2005 18:34:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=127





------- Additional Comments From dbarrera@xxxxxxxxxx  2005-07-29 18:34 -------
The third time, Dom0 did not crash, but a trace was generated on the serial
console while copying the same file over NFS.

(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) CPU:    0
(XEN) EIP:    e030:[<ffffffff802c5cee>] ???
(XEN) EFLAGS: 0000000000010207
(XEN) rax: 000000000000004a   rbx: ffffffff8048cf80   rcx: 000000000000004b  
rdx: 000000000000004a
(XEN) rsi: ffff8800099cae58   rdi: 000000000000004b   rbp: 0000000000000000  
rsp: ffff8800099cae58
(XEN) r8:  ffff88000b100000   r9:  ffff8800099cae58   r10: 000000000000007f  
r11: ffffffff802c4ff0
(XEN) r12: 000000000000004b   r13: 0000000000000008   r14: 0000000000000000  
r15: 0000000000000001
(XEN) Xen stack trace from rsp=ffff8800099cae58:
(XEN)    8000000003c32025 0000000000000000 8000000002ca4025 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)    800000000750e025 8000000007e6e025 8000000002fb6025 0000000000000000
0000000000000000 0000000000000000 0000000000000000 800000003ce8e025
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 00161c5c00161c5b 00161c5e00161c5d 00161c6000161c5f
(XEN)    00161c6200161c61 00161c6400161c63 00161c6600161c65 00161c6800161c67
00161c6a00161c69 00161c6c00161c6b 00161c6e00161c6d 0000000000161c6f
90000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000 0000000000000000
0000000000000000 00000




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

<Prev in Thread] Current Thread [Next in Thread>