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

[Guillaume Thouvenin <guillaume.thouvenin@xxxxxxxx>]

On Fri, 13 Jan 2006 10:10:59 +0000
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

> 
> On 13 Jan 2006, at 09:59, Guillaume Thouvenin wrote:
> 
> > 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
> 
> There's a changeset (8577) queued up in our staging tree that should 
> hopefully fix this.

I tested the changset 8612 but unfortunately the problem is still there.

Here is the report:

 (XEN) CPU:    3
(XEN) RIP:    e010:[<ffff8300001101f2>] desched_extra_dom+0xc2/0x190
(XEN) RFLAGS: 0000000000010006   CONTEXT: hypervisor
(XEN) rax: 00000004c4b40000   rbx: ffff830000ff8f00   rcx: ffff830000ff8f30
(XEN) rdx: 0000000000000000   rsi: 0000000000020000   rdi: 00000067879b972c
(XEN) rbp: 00000067879b972c   rsp: ffff8300001dbe20   r8:  ffff8300001eec80
(XEN) r9:  ffff830000fce080   r10: 0000000000000001   r11: 0000000000000001
(XEN) r12: ffff830000ff8f10   r13: 0000000000000003   r14: 0000000000000003
(XEN) r15: ffff830000180f80   cr0: 000000008005003b   cr3: 00000001059b2000
(XEN) Xen stack trace from rsp=ffff8300001dbe20:
(XEN)    ffff83000010f7b6 ffff8300001dc080 ffff8300001dc080 ffff83000011a3f3
(XEN)    0000000000000000 ffff830000ff8f20 ffff830000ff8f30 ffff830000180fa0
(XEN)    0000000000000003 00000067879b972c 0000000000000180 ffff830000fce080
(XEN)    ffff830000110d98 000000000007a120 ffff830000180e00 000000000007a120
(XEN)    ffff830000174ba0 0000000000000000 0000000000000003 ffff830000fce0a0
(XEN)    0000000000000000 0000000000000000 ffffffff8010002c 00000000ffffffff
(XEN)    0000ffffffff8010 ffffffff803affb0 ffff8300001109f5 00000000ffffffff
(XEN)    ffff830000110a7b ffffffff803affb0 ffff830000fce080 ffffffff802f7600
(XEN)    ffff8300001384ac ffffffff803affb0 0000ffffffff8010 00000000ffffffff
(XEN)    ffffffff8010002c ffffffff802f7600 00000000ffffffff 0000000000000246
(XEN)    0000000000000001 00000000ffff98b9 0000000000000180 0000000000000000
(XEN)    ffffffff8010fc5f 0000000000000000 0000000000000000 0000000000000001
(XEN)    0000010000000000 ffffffff8010fc5f 000000000000e033 0000000000000246
(XEN)    ffffffff803aff80 000000000000e02b 0000000000000000 0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000003 ffff830000fce080
(XEN) Xen call trace:
(XEN)    [<ffff8300001101f2>] desched_extra_dom+0xc2/0x190
(XEN)    [<ffff83000010f7b6>] sedf_do_schedule+0xc6/0x200
(XEN)    [<ffff83000011a3f3>] context_switch+0x173/0x1a0
(XEN)    [<ffff830000110d98>] __enter_scheduler+0x78/0x250
(XEN)    [<ffff8300001109f5>] do_block+0x85/0x90
(XEN)    [<ffff830000110a7b>] do_sched_op+0x7b/0x110
(XEN)    [<ffff8300001384ac>] 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) ************************************


Hope this help,
Best regards,
Guillaume

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