[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Hypervisor crash(!) on xl cpupool-numa-split




Do I understand correctly?
No crash with only dom0_max_vcpus= and no crash with only dom0_mem= ?
Yes, see my previous mail to George.


Could you try this patch?
Ok, the crash dump is as follows:
(XEN) Xen BUG at sched_credit.c:384
(XEN) ----[ Xen-4.1.0-rc2-pre  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    2
(XEN) RIP:    e008:[<ffff82c480117fa0>] csched_alloc_pdata+0x146/0x17f
(XEN) RFLAGS: 0000000000010093   CONTEXT: hypervisor
(XEN) rax: ffff830434322000   rbx: ffff830434418748   rcx: 0000000000000024
(XEN) rdx: ffff82c4802d3ec0   rsi: 0000000000000003   rdi: ffff8304343c9100
(XEN) rbp: ffff83043457fce8   rsp: ffff83043457fca8   r8:  0000000000000001
(XEN) r9:  ffff830434418748   r10: ffff82c48021a0a0   r11: 0000000000000286
(XEN) r12: 0000000000000024   r13: ffff83123a3b2b60   r14: ffff830434418730
(XEN) r15: 0000000000000024   cr0: 000000008005003b   cr4: 00000000000006f0
(XEN) cr3: 00000008061df000   cr2: ffff8817a21f87a0
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff83043457fca8:
(XEN)    ffff83043457fcb8 ffff83123a3b2b60 0000000000000286 0000000000000024
(XEN)    ffff830434418820 ffff83123a3b2a70 0000000000000024 ffff82c4802b0880
(XEN)    ffff83043457fd58 ffff82c48011fa63 ffff82f60102aa80 0000000000081554
(XEN)    ffff8300c7cfa000 0000000000000000 0000400000000000 ffff82c480248e00
(XEN)    0000000000000002 0000000000000024 ffff830434418820 0000000000305000
(XEN)    ffff82c4802550e4 ffff82c4802b0880 ffff83043457fd78 ffff82c48010188c
(XEN)    ffff83043457fe40 0000000000000024 ffff83043457fdb8 ffff82c480101b94
(XEN)    ffff83043457fdb8 ffff82c4801836f2 fffffffe00000286 ffff83043457ff18
(XEN)    0000000002170004 0000000000305000 ffff83043457fef8 ffff82c480125281
(XEN)    ffff83043457fdd8 0000000180153c9d 0000000000000000 ffff82c4801068f8
(XEN)    0000000000000296 ffff8300c7e0a1c8 aaaaaaaaaaaaaaaa 0000000000000000
(XEN)    ffff88007d1ac170 ffff88007d1ac170 ffff83043457fef8 ffff82c480113d8a
(XEN)    ffff83043457fe78 ffff83043457fe88 0000000800000012 0000000600000004
(XEN)    0000000000000000 ffffffff00000024 0000000000000000 00007fac2e0e5a00
(XEN)    0000000002170000 0000000000000000 0000000000000000 ffffffffffffffff
(XEN)    0000000000000000 0000000000000080 000000000000002f 0000000002170004
(XEN)    0000000002172004 0000000002174004 00007fff878f1c80 0000000000000033
(XEN)    ffff83043457fed8 ffff8300c7e0a000 00007fff878f1b30 0000000000305000
(XEN)    0000000000000003 0000000000000003 00007cfbcba800c7 ffff82c480207dd8
(XEN)    ffffffff8100946a 0000000000000023 0000000000000003 0000000000000003
(XEN) Xen call trace:
(XEN)    [<ffff82c480117fa0>] csched_alloc_pdata+0x146/0x17f
(XEN)    [<ffff82c48011fa63>] schedule_cpu_switch+0x75/0x1eb
(XEN)    [<ffff82c48010188c>] cpupool_assign_cpu_locked+0x44/0x8b
(XEN)    [<ffff82c480101b94>] cpupool_do_sysctl+0x1fb/0x461
(XEN)    [<ffff82c480125281>] do_sysctl+0x921/0xa30
(XEN)    [<ffff82c480207dd8>] syscall_enter+0xc8/0x122
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 2:
(XEN) Xen BUG at sched_credit.c:384
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

Regards,
Andre.


diff -r b59f04eb8978 xen/common/schedule.c
--- a/xen/common/schedule.c     Fri Jan 21 18:06:23 2011 +0000
+++ b/xen/common/schedule.c     Fri Jan 28 12:42:46 2011 +0100
@@ -1301,7 +1301,9 @@ void schedule_cpu_switch(unsigned int cp

      idle = idle_vcpu[cpu];
      ppriv = SCHED_OP(new_ops, alloc_pdata, cpu);
+    BUG_ON(ppriv == NULL);
      vpriv = SCHED_OP(new_ops, alloc_vdata, idle, idle->domain->sched_priv);
+    BUG_ON(vpriv == NULL);

      pcpu_schedule_lock_irqsave(cpu, flags);





--
Andre Przywara
AMD-OSRC (Dresden)
Tel: x29712


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.