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

Re: [Xen-devel] sedf scheduler may cause a CPU fatal trap

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] sedf scheduler may cause a CPU fatal trap
From: Guillaume Thouvenin <guillaume.thouvenin@xxxxxxxx>
Date: Fri, 13 Jan 2006 10:59:09 +0100
Cc: khoa@xxxxxxxxxx, Gerrit Huizenga <gh@xxxxxxxxxx>, ncmike@xxxxxxxxxx
Delivery-date: Fri, 13 Jan 2006 10:05:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060113093336.4f0f1da6@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: BULL SA.
References: <20060110100113.39b3adf1@xxxxxxxxxxxxxxxxxxxxxxxx> <20060113093336.4f0f1da6@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I ran two commands on the xen-unstable.hg that produced the CPU fatal
trap. I tested the changset 8571 on a x86_64 xeon bi-processors with HT
enabled. I only started one unprivileged domain. The two commands are:

   # xm sched-sedf 1 20000000 5000000 0 0 0
   # xm sched-sedf 1 20000000 0 0 1 0

And I got the following report:

(XEN) CPU:    3
(XEN) RIP:    e010:[<ffff830000110972>] desched_extra_dom+0xc2/0x190
(XEN) RFLAGS: 0000000000010006   CONTEXT: hypervisor
(XEN) rax: 00000004c4b40000   rbx: ffff830000ff8f00   rcx: ffff830000ff8f30
(XEN) rdx: 0000000000000000   rsi: 0000000000001000   rdi: 00000044a62c0b62
(XEN) rbp: 00000044a62c0b62   rsp: ffff8300001dbe20   r8:  ffff8300001eef00
(XEN) r9:  ffff8300001e6080   r10: 0000000000000001   r11: 0000000000000001
(XEN) r12: ffff830000ff8f10   r13: 0000000000000003   r14: 0000000000000003
(XEN) r15: ffff830000181f80   cr0: 000000008005003b   cr3: 0000000104f07000
(XEN) Xen stack trace from rsp=ffff8300001dbe20:
(XEN)    ffff83000010ff36 0000000000000086 ffff830000ff8f20 ffff83000011a153
(XEN)    0000000000000008 ffff830000ff8f20 ffff830000ff8f30 ffff830000181fa0
(XEN)    0000000000000003 00000044a62c0b62 0000000000000180 ffff8300001e6080
(XEN)    ffff8300001114a8 0000000000000206 ffff830000181e00 ffff88001fa55b68
(XEN)    ffff8300001dbec8 0000000000000003 ffff8300001e60a0 0000000000000003
(XEN)    0000000000000000 0000000000000000 ffffffff8010002c 00000000ffffffff
(XEN)    0000ffffffff8010 ffffffff803affb0 ffff83000011110b 00000000ffffffff
(XEN)    ffff83000011119b ffffffff803affb0 ffff8300001e6080 ffffffff802f7580
(XEN)    ffff83000013806c ffffffff803affb0 0000ffffffff8010 00000000ffffffff
(XEN)    ffffffff8010002c ffffffff802f7580 00000000ffffffff 0000000000000246
(XEN)    0000000000000001 00000000ffffabf1 00000000000002b0 0000000000000000
(XEN)    ffffffff8010fc5f 0000000000000000 0000000000000000 0000000000000001
(XEN)    0000010000000000 ffffffff8010fc5f 000000000000e033 0000000000000246
(XEN)    ffffffff803aff80 000000000000e02b 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000003 ffff8300001e6080
(XEN) Xen call trace:
(XEN)    [<ffff830000110972>] desched_extra_dom+0xc2/0x190
(XEN)    [<ffff83000010ff36>] sedf_do_schedule+0xc6/0x200
(XEN)    [<ffff83000011a153>] context_switch+0x173/0x1a0
(XEN)    [<ffff8300001114a8>] __enter_scheduler+0x78/0x260
(XEN)    [<ffff83000011110b>] do_block+0x7b/0x90
(XEN)    [<ffff83000011119b>] do_sched_op+0x7b/0x110
(XEN)    [<ffff83000013806c>] syscall_enter+0x5c/0x61
(XEN)
(XEN) ************************************
(XEN) CPU3 FATAL TRAP 0 (divide error), ERROR_CODE 0000, IN INTERRUPT CONTEXT.
(XEN) System shutting down -- need manual reset.
(XEN) ************************************


Best regards,
Guillaume

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