WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] BUG: unable to handle kernel paging request - balloon_in

To: Scott Garron <xen-devel@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 4 May 2011 15:35:50 -0400
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Delivery-date: Wed, 04 May 2011 12:36:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DC1A6AC.3080305@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110426031545.GB20779@xxxxxxxxxxxx> <4DB6522A.9000304@xxxxxxxxxxxxxxxxxx> <20110427200937.GA19853@xxxxxxxxxxxx> <4DB8AAA6.4050808@xxxxxxxxxxxxxxxxxx> <20110428183019.GA9852@xxxxxxxxxxxxxxxxxxxxxxxxxxxx@sce.pridelands.org> <c99e08eb-34b3-462e-b7b2-278546bb4b28@xxxxxxxxxxxxxxxxxxxxxxx@sce.pridelands.org> <4ebbb8ac-77a5-4525-b69e-273c177c05e2@default> <4DBB44ED.2020701@xxxxxxxxxxxxxxxxxx> <20110504155817.GA28022@xxxxxxxxxxxx> <4DC1A6AC.3080305@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, May 04, 2011 at 03:19:08PM -0400, Scott Garron wrote:
> On 05/04/2011 11:58 AM, Konrad Rzeszutek Wilk wrote:
> >It tells us that the pages have been indeed filled up with the right values.
> >But perhaps the values for the entries past the 4G are filled with zero, 
> >which
> >might be the case as in (pte_pfn_to_mfn):
> 
>      Just FYI, the machine has exactly 4G of RAM - 2 on one CPU, 2 on
> the other (two socket motherboard, single core each).
> 
> >Anyhow, try this patch below. Should give us some ideas. Not compile tested.
                                                                ^^^^^^^^^^ 

The __func__ can be just __FUNCTION__ and the reset can be ignored (I think)

> 
> >+                    printk(KERN_INFO "%s: 0x%lx is INVALID for %llx\n",
> >+                            ___func__, pfn, (unsigned long)val);
> 
>      The compile complained about __func__ not being declared and
> exited with an error.
> 
> >+    printk(KERN_INFO "%s: %lx, %lx\n", __func__, u.ptr, u.val);
> 
>      The compile also warned about %lx expecting 'long unsigned int',
> but argument 3 and 4 are 'uint64_t'.
> 
> arch/x86/xen/mmu.c: In function ‘pte_pfn_to_mfn’:
> arch/x86/xen/mmu.c:810:5: error: ‘___func__’ undeclared (first use
> in this function)
> arch/x86/xen/mmu.c:810:5: note: each undeclared identifier is
> reported only once for each function it appears in
> arch/x86/xen/mmu.c: In function ‘xen_set_pud_hyper’:
> arch/x86/xen/mmu.c:940:2: warning: format ‘%lx’ expects type ‘long
> unsigned int’, but argument 3 has type ‘uint64_t’
> arch/x86/xen/mmu.c:940:2: warning: format ‘%lx’ expects type ‘long
> unsigned int’, but argument 4 has type ‘uint64_t’
> make[2]: *** [arch/x86/xen/mmu.o] Error 1
> make[1]: *** [arch/x86/xen] Error 2
> make: *** [arch/x86] Error 2
> make: *** Waiting for unfinished jobs....
> 
> 
> -- 
> Scott Garron
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel