Re: [Xen-devel] BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

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