Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-bugs

[Xen-bugs] [Bug 850] New: Random crash after relaunching a xen domU halt

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 850] New: Random crash after relaunching a xen domU halted
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 5 Jan 2007 08:55:11 -0800
Delivery-date: Fri, 05 Jan 2007 08:55:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=850

           Summary: Random crash after relaunching a xen domU halted
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: baco@xxxxxxxx
                CC: baco@xxxxxxxxxxxxx


I couldn't reproduce this again
just after launching again a domU who 
has been halted. 

vmu1 kernel: kernel BUG at drivers/xen/core/evtchn.c:481!
vmu1 kernel: invalid opcode: 0000 [#1]
vmu1 kernel: SMP
vmu1 kernel: CPU:    1
vmu1 kernel: EIP is at retrigger+0x1f/0x35
vmu1 kernel: eax: 00000000  ebx: 02080000  ecx: 0000003e  edx: f5746000
vmu1 kernel: esi: c06ac900  edi: 0000012a  ebp: ed78bf04  esp: ed78beb4
vmu1 kernel: ds: 007b  es: 007b  ss: 0069
vmu1 kernel: Process xenwatch (pid: 11[#0], ti=ed78a000 task=c0f07190
task.ti=ed78a000)
vmu1 kernel: Stack: c01410f5 c06ac900 0000012a 00000000 c0140ab3 ec81cc00
00000000 ec81cc00
vmu1 kernel:        c039b51f 00000000 c039ba86 ec81cc00 c015d1df fffffffe
eaa54dc0 eccc1e00
vmu1 kernel:        c0394a9f 00000000 ed78bf2c eaab5360 c0390009 0000000c
0000003e eaab5360
vmu1 kernel: Call Trace:
vmu1 kernel: Code: 89 c2 89 d8 e8 6f ff ff ff 59 5b c3 0f b7 0c 85 60 08 73 c0
8b 15 e4 8e 5f c0 85 c9 74 1d 0f a3 8a 80 08 00 00 19 c0 85 c0 75 08 <0f> 0b e1
01 12 d4 57 c0 f0 0f ab8a 00 08 00 00 b8 01 00 00 00
vmu1 kernel: EIP: [retrigger+31/53] retrigger+0x1f/0x35 SS:ESP 0069:ed78beb4

After this...
Dom0 and all DomU down ping timeout..
hard reboot or xen dom0..


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- 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>