From: Ben Guthro <ben@guthro.net>
To: Xen Devel <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: dump with xen-unstable & linux 3.2.17
Date: Thu, 17 May 2012 17:20:42 -0400 [thread overview]
Message-ID: <CAOvdn6V1xSRjWEMPG8Mo1qZUco2NQC-eLWOJ7paM4329tjkFfg@mail.gmail.com> (raw)
I'm attempting to update the Xen I'm using, and am having an issue with S3.
Konrad - I know you've been down this path before - so I'm hoping you
might have some insight, given the stack below
The linux tree also has an older version of Konrad's acpi-s3
development branches (it was v7)
Upon resuming from S3 - Xen panics with the following stack. I'm
guessing it has something to do with some of the pcpu work going on
recently - but haven't been tracking this too closely, so am not sure.
The same kernel with Xen 4.0.x works OK.
(XEN) Assertion '!cpumask_empty(&cpus) && cpumask_test_cpu(cpu,
&cpus)' failed at sched_credit.c:477
(XEN) ----[ Xen-4.2-unstable x86_64 debug=y Not tainted ]----
(XEN) CPU: 1
(XEN) RIP: e008:[<ffff82c48011a793>] _csched_cpu_pick+0x135/0x552
(XEN) RFLAGS: 0000000000010002 CONTEXT: hypervisor
(XEN) rax: 0000000000000001 rbx: 0000000000000010 rcx: 0000000000000010
(XEN) rdx: 000000ffff rsi: 0000000000000010 rdi: 0000000000000000
(XEN) rbp: ffff83013e38fdd8 rsp: ffff83013e38fd08 r8: 0000000000000000
(XEN) r9: 000000000000003e r10: ffff82c480232480 r11: 0000000000000246
(XEN) r12: ffff82c480262820 r13: 0000000000000001 r14: ffff82c4803022e0
(XEN) r15: ffff83014c6f0068 cr0: 000000008005003b cr4: 00000000001026f0
(XEN) cr3: 0000000141a05000 cr2: 0000000000000000
(XEN) ds: 002b es: 002b fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff83013e38fd08:
(XEN) 0100000141a05000 ffff83013e38fd40 0000000000000297 ffff83013e38fd38
(XEN) ffff82c480125929 ffff830148ac2000 ffff83013e38fd78 5400000000000002
(XEN) 0000000000000282 ffff83013e38fd68 ffff82c480125929 ffff830148ac2000
(XEN) ffff83013e38fd98 ffff82c48012cd57 0000000000000000 0000000000000008
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000286 ffff83014c6f0068 ffff83014c6f0068 0000000000000001
(XEN) ffff82c4803022e0 ffff83014c6f0068 ffff83013e38fde8 ffff82c48011abbe
(XEN) ffff83013e38fe58 ffff82c48012399d ffff82c4803022e0 ffff82c4803022e0
(XEN) ffff82c4803022e0 ffff8300aa0fd000 00000000000fd060 0000000000000246
(XEN) ffff82c4801280c1 ffff8300aa0fd000 ffff82c4803022e0 ffff82c4802ec5c0
(XEN) ffff83014c6f0068002dc2e820 ffff83013e38fe88 ffff82c480123c57
(XEN) fffffffffffffffe ffff830148a36000 ffff8300aa0fd000 0000000000000000
(XEN) ffff83013e38fef8 ffff82c4801063f5 ffff83013e38ff18 ffffffff810030d2
(XEN) ffff8300aa0fd000 0000000000000000 ffff83013e38ff08 ffff82c480185ff0
(XEN) ffffffff81ab0020 ffff8300aa0fd000 0000000000000001 000000000000
(XEN) 0000000000000000 ffff88002dc2e820 00007cfec1c700c7 ffff82c480228f78
(XEN) ffffffff8100130a 0000000000000018 ffff88002dc2e820 0000000000000000
(XEN) 0000000000000000 0000000000000001 ffff88002786dda0 ffff88002dc2bdc0
(XEN) 0000000000000246 00000000ffffffff 0000000000000040 0000000000000000
(XEN) 0000000000000018 ffffffff8100130a 0000000000000000 0000000000000001
(XEN) Xen call trace:
(XEN) [<ffff82c48011a793>] _csched_cpu_pick+0x135/0x552
(XEN) [<ffff82c48011abbe>] csched_cpu_pick+0xe/0x10
(XEN) [<ffff82c48012399d>] vcpu_migrate+0x19f/0x346
(XEN) [<ffff82c480123c57>] vcpu_force_reschedule+0xa4/0xb6
(XEN) [<ffff82c48f5>] do_vcpu_op+0x2c9/0x452
(XEN) [<ffff82c480228f78>] syscall_enter+0xc8/0x122
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) Assertion '!cpumask_empty(&cpus) && cpumask_test_cpu(cpu,
&cpus)' failed at sched_credit.c:477
(XEN) ****************************************
next reply other threads:[~2012-05-17 21:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 21:20 Ben Guthro [this message]
2012-05-21 14:55 ` dump with xen-unstable & linux 3.2.17 Jan Beulich
2012-05-21 19:12 ` Ben Guthro
2012-05-21 19:49 ` Ben Guthro
2012-05-22 15:38 ` Ben Guthro
2012-05-22 16:08 ` Jan Beulich
2012-05-22 16:21 ` Ben Guthro
2012-05-22 17:34 ` Konrad Rzeszutek Wilk
2012-05-22 17:55 ` Ben Guthro
2012-05-22 18:00 ` Konrad Rzeszutek Wilk
2012-05-22 18:26 ` Ben Guthro
2012-05-22 21:00 ` Ben Guthro
2012-05-23 9:39 ` Jan Beulich
2012-05-23 11:00 ` Juergen Gross
2012-05-25 13:20 ` Ben Guthro
2012-05-31 15:52 ` Ben Guthro
2012-05-31 16:06 ` Jan Beulich
2012-05-31 16:18 ` Ben Guthro
2012-06-01 6:54 ` Dietmar Hahn
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=CAOvdn6V1xSRjWEMPG8Mo1qZUco2NQC-eLWOJ7paM4329tjkFfg@mail.gmail.com \
--to=ben@guthro.net \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).