From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: multicalls.c warning in xen_mc_flush Date: Tue, 22 May 2012 14:36:59 -0400 Message-ID: <20120522183659.GA24324@phenom.dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: William Dauchy Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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: > [] warn_slowpath_common+0x6d/0xa0 > [] ? xen_mc_flush+0x12a/0x140 > [] ? xen_mc_flush+0x12a/0x140 > [] warn_slowpath_null+0x1d/0x20 > [] xen_mc_flush+0x12a/0x140 > [] xen_set_pmd_hyper+0x75/0x80 > [] set_pmd_pfn+0x9e/0xf0 > [] init_alloc_remap+0x1c3/0x237 > [] x86_numa_init+0x378/0x691 > [] ? xen_set_fixmap+0xa6/0x160 > [] initmem_init+0xb/0xd6 > [] ? early_acpi_boot_init+0x6e/0xbe > [] ? acpi_boot_table_init+0x36/0x7d > [] setup_arch+0xb30/0xbe7 > [] start_kernel+0x76/0x2ef > [] i386_start_kernel+0xa9/0xb0 > [] xen_start_kernel+0x546/0x54e > > > Regards, > -- > William > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel