From: Dario Faggioli <dario.faggioli@citrix.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: andrew.cooper3@citrix.com, boris.ostrovsky@oracle.com,
keir@xen.org, JBeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v3] x86: correct socket_cpumask allocation
Date: Fri, 10 Jul 2015 16:29:40 +0200 [thread overview]
Message-ID: <1436538580.22672.420.camel@citrix.com> (raw)
In-Reply-To: <1436451837-26171-1-git-send-email-chao.p.peng@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 4089 bytes --]
On Thu, 2015-07-09 at 22:23 +0800, Chao Peng wrote:
> For booting cpu, the socket number is not needed to be 0 so
> it needs to be computed by cpu number.
>
This made my system boot, yes... but now it does not shutdown! :-/
I'm attaching the splat I see, reliably, on my testbox.
I'll try have a look at this, but feel free (especially Chao) to preempt
me, if you get to the solution quicker.
Dario
(XEN) ----[ Xen-4.6-unstable x86_64 debug=y Tainted: C ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82d0801886aa>] cpu_smpboot_free+0x2b/0x255
(XEN) RFLAGS: 0000000000010206 CONTEXT: hypervisor
(XEN) rax: ffff83032072a5c0 rbx: 00000000ffffffff rcx: 0000000000000000
(XEN) rdx: ffff82d08031ff00 rsi: 0000000000008008 rdi: 0000000000000001
(XEN) rbp: ffff8300dbaefd40 rsp: ffff8300dbaefd20 r8: ffff830320729df0
(XEN) r9: 00000000003206fd r10: 0000000000000001 r11: 0080000000000000
(XEN) r12: 0000000000000001 r13: ffff82d08029e348 r14: 0000000000008008
(XEN) r15: 0000000000008000 cr0: 000000008005003b cr4: 00000000000026e0
(XEN) cr3: 00000000dba9c000 cr2: ffff830b2072a5b8
(XEN) ds: 002b es: 002b fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from rsp=ffff8300dbaefd20:
(XEN) 0000000000008008 0000000000000001 ffff82d08029f140 ffff82d08029e348
(XEN) ffff8300dbaefd70 ffff82d080189225 ffff82d08029f148 ffff82d08029f140
(XEN) ffff82d08029e348 0000000000008008 ffff8300dbaefdc0 ffff82d08011c019
(XEN) 0000000000000000 0000000000000001 ffff8300dbaefdb0 0000000000000000
(XEN) 0000000000000000 0000000000000001 ffff82d080334a88 ffffffffffffffff
(XEN) ffff8300dbaefe00 ffff82d08010153e ffff8300dbaefdf0 ffff82d08029e340
(XEN) 0000000052414d44 0000000000000001 0000000000000001 ffff82d08028aca0
(XEN) ffff8300dbaefe30 ffff82d080101744 0000000000000000 0000000000000005
(XEN) ffff82d080334b60 ffff82d080334a88 ffff8300dbaefe80 ffff82d0801a8967
(XEN) ffff8300dbaefe60 ffff82d080165bee ffff82d080334a88 ffff830322da1400
(XEN) ffff8300dbb3b000 ffff82d080334b60 ffff82d080334a88 ffffffffffffffff
(XEN) ffff8300dbaefea0 ffff82d080106212 ffff8300dbb3b1d0 0000000000000000
(XEN) ffff8300dbaefec0 ffff82d08012f8ae ffff8300dbaefec0 ffff82d080334b70
(XEN) ffff8300dbaefef0 ffff82d08012fbe4 0000000cdb9d803e ffff8300dbae8000
(XEN) 0000000cdb9d803e ffff8300dbdf4000 ffff8300dbaeff10 ffff82d0801617e0
(XEN) ffff82d08012cb4c ffff8300dbdf4000 ffff8300dbaefe10 00000000001d6000
(XEN) 00000000ffffffed 00000000001d6000 0000000000000000 ffff880012ae3eb0
(XEN) 0000000000000000 0000000000000246 0000000000000040 0000000000000000
(XEN) 00000000000000d2 0000000000000000 ffffffff810013aa 0100000000000000
(XEN) 00000000deadbeef 00000000deadbeef 0000010000000000 ffffffff810013aa
(XEN) Xen call trace:
(XEN) [<ffff82d0801886aa>] cpu_smpboot_free+0x2b/0x255
(XEN) [<ffff82d080189225>] cpu_smpboot_callback+0x317/0x327
(XEN) [<ffff82d08011c019>] notifier_call_chain+0x67/0x87
(XEN) [<ffff82d08010153e>] cpu_down+0xd9/0x12c
(XEN) [<ffff82d080101744>] disable_nonboot_cpus+0x93/0x138
(XEN) [<ffff82d0801a8967>] enter_state_helper+0xbd/0x365
(XEN) [<ffff82d080106212>] continue_hypercall_tasklet_handler+0x4a/0xb1
(XEN) [<ffff82d08012f8ae>] do_tasklet_work+0x78/0xab
(XEN) [<ffff82d08012fbe4>] do_tasklet+0x5e/0x8a
(XEN) [<ffff82d0801617e0>] idle_loop+0x56/0x6b
(XEN)
(XEN) Pagetable walk from ffff830b2072a5b8:
(XEN) L4[0x106] = 00000000dba9a063 ffffffffffffffff
(XEN) L3[0x02c] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: ffff830b2072a5b8
(XEN) ****************************************
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-10 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 14:23 [PATCH v3] x86: correct socket_cpumask allocation Chao Peng
2015-07-09 15:16 ` Andrew Cooper
2015-07-09 15:36 ` Boris Ostrovsky
2015-07-10 14:29 ` Dario Faggioli [this message]
2015-07-10 14:47 ` Andrew Cooper
2015-07-10 14:57 ` Dario Faggioli
2015-07-10 15:13 ` Jan Beulich
2015-07-10 15:25 ` Jan Beulich
2015-07-10 16:03 ` Dario Faggioli
2015-07-13 3:19 ` Chao Peng
2015-07-10 15:33 ` Dario Faggioli
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=1436538580.22672.420.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chao.p.peng@linux.intel.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.org \
/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).