xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: multicalls.c warning in xen_mc_flush
Date: Tue, 22 May 2012 14:36:59 -0400	[thread overview]
Message-ID: <20120522183659.GA24324@phenom.dumpdata.com> (raw)
In-Reply-To: <CAJ75kXYXvVA3Xd9evNkvkFL+JuGLcFG=DwHbXAxsLsZ0pKk1Sg@mail.gmail.com>

On Tue, May 22, 2012 at 03:04:17PM +0200, William Dauchy wrote:
> Hello,
> 
> I'm getting a call trace when booting a dom0 v3.3.7 (x86_32) under xen 4.1.2.
> It is about multicalls.c:129. I tried with MC_DEBUG = 1 but it appears
> that b->mcidx = 1 when getting this call trace.
> Does anybody have any clue?

Yes. Do you have CONFIG_NUMA enabled? If you disable it, do the messages
disappear?

> 
> 
> WARNING: at /arch/x86/xen/multicalls.c:129 xen_mc_flush+0x12a/0x140()
> Hardware name: C6100
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 3.3.7-i386 #125
> Call Trace:
>  [<c102f34d>] warn_slowpath_common+0x6d/0xa0
>  [<c100384a>] ? xen_mc_flush+0x12a/0x140
>  [<c100384a>] ? xen_mc_flush+0x12a/0x140
>  [<c102f39d>] warn_slowpath_null+0x1d/0x20
>  [<c100384a>] xen_mc_flush+0x12a/0x140
>  [<c1006035>] xen_set_pmd_hyper+0x75/0x80
>  [<c102c4ee>] set_pmd_pfn+0x9e/0xf0
>  [<c14e68c7>] init_alloc_remap+0x1c3/0x237
>  [<c14e6315>] x86_numa_init+0x378/0x691
>  [<c1004af6>] ? xen_set_fixmap+0xa6/0x160
>  [<c14e6639>] initmem_init+0xb/0xd6
>  [<c14dea61>] ? early_acpi_boot_init+0x6e/0xbe
>  [<c14dede0>] ? acpi_boot_table_init+0x36/0x7d
>  [<c14d7796>] setup_arch+0xb30/0xbe7
>  [<c14d1566>] start_kernel+0x76/0x2ef
>  [<c14d10ba>] i386_start_kernel+0xa9/0xb0
>  [<c14d4a66>] xen_start_kernel+0x546/0x54e
> 
> 
> Regards,
> -- 
> William
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-05-22 18:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 13:04 multicalls.c warning in xen_mc_flush William Dauchy
2012-05-22 18:36 ` Konrad Rzeszutek Wilk [this message]
2012-05-22 22:46   ` William Dauchy
2012-05-25 21:01     ` Konrad Rzeszutek Wilk
2012-05-25 21:17       ` William Dauchy
2012-05-29 11:39       ` William Dauchy
2012-05-30 14:18         ` Konrad Rzeszutek Wilk
2012-05-30 21:29           ` William Dauchy
2012-05-31 15:10             ` Konrad Rzeszutek Wilk

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=20120522183659.GA24324@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=wdauchy@gmail.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).