From: Andre Przywara <andre.przywara@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Hypervisor crash(!) on xl cpupool-numa-split
Date: Fri, 28 Jan 2011 00:18:18 +0100 [thread overview]
Message-ID: <4D41FD3A.5090506@amd.com> (raw)
Hi,
when I boot my machine without restricting Dom0 (dom0_mem=
dom0_max_vcpus=) I get an _hypervisor_ crash when I run
# xl cpupool-numa-split
If Dom0's resources are limited on the Xen cmdline, everything works fine.
The crashdump points to a scheduling problem with weights, so I assume
the NUMA distribution algorithm some fools the hypervisor completely.
I will investigate this further tomorrow, but maybe someone has some
good idea.
Regards,
Andre.
root@dosorca:/data/images# xl cpupool-numa-split
(XEN) Xen BUG at sched_credit.c:990
(XEN) ----[ Xen-4.1.0-rc2-pre x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82c4801180f8>] csched_acct+0x11f/0x419
(XEN) RFLAGS: 0000000000010006 CONTEXT: hypervisor
(XEN) rax: 0000000000000010 rbx: 0000000000000f00 rcx: 0000000000000100
(XEN) rdx: 0000000000001000 rsi: ffff830437ffa600 rdi: 0000000000000010
(XEN) rbp: ffff82c480297e10 rsp: ffff82c480297d80 r8: 0000000000000100
(XEN) r9: 0000000000000006 r10: ffff82c4802d4100 r11: 000000afc7df0edf
(XEN) r12: ffff830437ffa5e0 r13: ffff82c480117fd9 r14: ffff830437f9f2e8
(XEN) r15: ffff830434321ec0 cr0: 000000008005003b cr4: 00000000000006f0
(XEN) cr3: 000000080df4e000 cr2: ffff88179af79618
(XEN) ds: 002b es: 002b fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff82c480297d80:
(XEN) 0000000000000282 fffffed4802d3f80 0000000000000eff ffff830437ffa5e0
(XEN) ffff830437ffa5e8 ffff830437ffa870 ffff830437ffa5e0 0000000000000282
(XEN) ffff830437ffa5e8 00002a3037ffa870 00000f0000000f00 0000000000000000
(XEN) ffff82c400000000 ffff82c4802d3f80 ffff830437ffa5e0 ffff82c480117fd9
(XEN) ffff830437f9f2e8 ffff830437f9f2e0 ffff82c480297e40 ffff82c480125f34
(XEN) 0000000000000002 ffff830437ffa600 ffff82c4802d3f80 000000afb6f8667f
(XEN) ffff82c480297e90 ffff82c480126259 ffff82c48024ae20 ffff82c4802d3f80
(XEN) ffff830437f9f2e0 0000000000000000 0000000000000000 ffff82c4802b0880
(XEN) ffff82c480297f18 ffffffffffffffff ffff82c480297ed0 ffff82c480123327
(XEN) ffff82c4802d4a00 ffff82c480297f18 ffff82c48024ae20 ffff82c480297f18
(XEN) 000000afb6abd652 ffff82c4802d3ec0 ffff82c480297ee0 ffff82c4801233a2
(XEN) ffff82c480297f10 ffff82c4801563f5 0000000000000000 ffff8300c7cd6000
(XEN) 0000000000000000 ffff8300c7ad4000 ffff82c480297d48 0000000000000000
(XEN) 0000000000000000 0000000000000000 ffffffff81a69060 ffff8817a8503f10
(XEN) ffff8817a8503fd8 0000000000000246 ffff8817a8503e80 ffff880000000001
(XEN) 0000000000000000 0000000000000000 ffffffff810093aa 000000aafab2f86e
(XEN) 00000000deadbeef 00000000deadbeef 0000010000000000 ffffffff810093aa
(XEN) 000000000000e033 0000000000000246 ffff8817a8503ef8 000000000000e02b
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 ffff8300c7cd6000 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<ffff82c4801180f8>] csched_acct+0x11f/0x419
(XEN) [<ffff82c480125f34>] execute_timer+0x4e/0x6c
(XEN) [<ffff82c480126259>] timer_softirq_action+0xf2/0x245
(XEN) [<ffff82c480123327>] __do_softirq+0x88/0x99
(XEN) [<ffff82c4801233a2>] do_softirq+0x6a/0x7a
(XEN) [<ffff82c4801563f5>] idle_loop+0x6a/0x6f
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at sched_credit.c:990
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
--
Andre Przywara
AMD-OSRC (Dresden)
Tel: x29712
next reply other threads:[~2011-01-27 23:18 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 23:18 Andre Przywara [this message]
2011-01-28 6:47 ` Hypervisor crash(!) on xl cpupool-numa-split Juergen Gross
2011-01-28 11:07 ` Andre Przywara
2011-01-28 11:44 ` Juergen Gross
2011-01-28 13:14 ` Andre Przywara
2011-01-31 7:04 ` Juergen Gross
2011-01-31 14:59 ` Andre Przywara
2011-01-31 15:28 ` George Dunlap
2011-02-01 16:32 ` Andre Przywara
2011-02-02 6:27 ` Juergen Gross
2011-02-02 8:49 ` Juergen Gross
2011-02-02 10:05 ` Juergen Gross
2011-02-02 10:59 ` Andre Przywara
2011-02-02 14:39 ` Stephan Diestelhorst
2011-02-02 15:14 ` Juergen Gross
2011-02-02 16:01 ` Stephan Diestelhorst
2011-02-03 5:57 ` Juergen Gross
2011-02-03 9:18 ` Juergen Gross
2011-02-04 14:09 ` Andre Przywara
2011-02-07 12:38 ` Andre Przywara
2011-02-07 13:32 ` Juergen Gross
2011-02-07 15:55 ` George Dunlap
2011-02-08 5:43 ` Juergen Gross
2011-02-08 12:08 ` George Dunlap
2011-02-08 12:14 ` George Dunlap
2011-02-08 16:33 ` Andre Przywara
2011-02-09 12:27 ` George Dunlap
2011-02-09 12:27 ` George Dunlap
2011-02-09 13:04 ` Juergen Gross
2011-02-09 13:39 ` Andre Przywara
2011-02-09 13:51 ` Andre Przywara
2011-02-09 14:21 ` Juergen Gross
2011-02-10 6:42 ` Juergen Gross
2011-02-10 9:25 ` Andre Przywara
2011-02-10 14:18 ` Andre Przywara
2011-02-11 6:17 ` Juergen Gross
2011-02-11 7:39 ` Andre Przywara
2011-02-14 17:57 ` George Dunlap
2011-02-15 7:22 ` Juergen Gross
2011-02-16 9:47 ` Juergen Gross
2011-02-16 13:54 ` George Dunlap
[not found] ` <4D6237C6.1050206@amd.c om>
2011-02-16 14:11 ` Juergen Gross
2011-02-16 14:28 ` Juergen Gross
2011-02-17 0:05 ` André Przywara
2011-02-17 7:05 ` Juergen Gross
2011-02-17 9:11 ` Juergen Gross
2011-02-21 10:00 ` Andre Przywara
2011-02-21 13:19 ` Juergen Gross
2011-02-21 14:45 ` Andre Przywara
2011-02-21 14:50 ` Juergen Gross
2011-02-08 12:23 ` Juergen Gross
2011-01-28 11:13 ` George Dunlap
2011-01-28 13:05 ` Andre Przywara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D41FD3A.5090506@amd.com \
--to=andre.przywara@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.