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 20] New: LTP fork05 test crashes dom0

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 20] New: LTP fork05 test crashes dom0
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 04 May 2005 20:08:11 +0000
Delivery-date: Wed, 04 May 2005 20:08:14 +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=20

           Summary: LTP fork05 test crashes dom0
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: pl@xxxxxxxxxx


I noticed this in the xen-unstable build for today (May 4, 2005) but it may have
been in the preious day as well.  It rebooted after the crash, forgot to set
this machine up so that it wouldn't do that.  In any case, it just started
failing within the past few days at the most.

Here's the serial console dump:
(XEN) BUG at domain.c:136
(XEN) CPU:    0
(XEN) EIP:    0808:[<ff105fee>]
(XEN) EFLAGS: 00010292   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: ffbf6900   ecx: 00000046   edx: 000002f8
(XEN) esi: ffbe6000   edi: fed18000   ebp: 000003d4   esp: ff103eb8
(XEN) ds: 0810   es: 0810   fs: 0810   gs: 0810   ss: 0810   cs: 0808
(XEN) Stack trace from ESP=ff103eb8:
(XEN)    ff143b4c ff143ba2 00000088 ffbf6b00 1a3d4061 000000b0 ffbe6000 
[ff11d42f]
(XEN)    1a3d4063 ffbf6900 e0000000 [ff1298a2] 10102000 00000000 f0000001 
ffbf6b00
(XEN)    00000001 fed17000 ffbf6900 ffbf5080 00007ff0 c0026f51 ffbf6900 
[ff122571]
(XEN)    ffbf6900 00000000 00000296 00000001 ffbf5080 00000001 c0026f50 10026000
(XEN)    00000001 ffbf6900 [ff11d663] 10026000 ffffffff 80000004 ffbf6900 
10026063
(XEN)    00000328 ffbf6b00 ffbf6900 3650001d 00000000 fe3f8ca0 00000000 ffbf5080
(XEN)    00000000 ff103fb8 00000000 00000000 c0026f50 00015fea 00015fea fed16bfc
(XEN)    15feabfc 00000000 ffbf5080 ffbf5080 00007ff0 c4aee590 c50a7f84 
[ff135093]
(XEN)    c50a7f58 00000002 00000000 00007ff0 c4aee590 c50a7f84 0000001a 000e0003
(XEN)    c042cdf5 00000061 00000246 c50a7f28 00000069 0000007b 0000007b 00000000
(XEN)    00000000 ffbf5080
(XEN) Call Trace from ESP=ff103eb8:
(XEN)    [<ff11d42f>] [<ff1298a2>] [<ff122571>] [<ff11d663>] [<ff135093>]

****************************************
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
Aieee! CPU0 is toast...
****************************************



------- 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>
  • [Xen-bugs] [Bug 20] New: LTP fork05 test crashes dom0, bugzilla-daemon <=