From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Scott Garron <xen-devel@sce.pridelands.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
xen-devel@lists.xensource.com,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39
Date: Wed, 4 May 2011 15:35:50 -0400 [thread overview]
Message-ID: <20110504193550.GB24996@dumpdata.com> (raw)
In-Reply-To: <4DC1A6AC.3080305@sce.pridelands.org>
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@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-04 19:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:04 BUG: unable to handle kernel paging request - balloon_init - xen-4.1.0 - 2.6.32.39 Scott Garron
2011-04-26 3:15 ` Konrad Rzeszutek Wilk
2011-04-26 5:03 ` Scott Garron
2011-04-27 20:09 ` Konrad Rzeszutek Wilk
2011-04-27 23:45 ` Scott Garron
[not found] ` <20110428183019.GA9852@dumpdata.com4DBA1EA4.5010004@sce.pridelands.org>
2011-04-28 18:30 ` Konrad Rzeszutek Wilk
2011-04-29 0:15 ` Scott Garron
2011-04-29 2:12 ` Scott Garron
2011-04-29 14:43 ` Dan Magenheimer
2011-04-29 16:56 ` Scott Garron
2011-04-29 19:38 ` Dan Magenheimer
2011-04-29 23:08 ` Scott Garron
2011-05-04 15:58 ` Konrad Rzeszutek Wilk
2011-05-04 19:19 ` Scott Garron
2011-05-04 19:35 ` Konrad Rzeszutek Wilk [this message]
2011-05-04 20:17 ` Scott Garron
2011-05-04 20:23 ` Konrad Rzeszutek Wilk
2011-05-04 21:55 ` Scott Garron
2011-05-04 22:16 ` Konrad Rzeszutek Wilk
2011-05-04 23:23 ` Scott Garron
2011-05-05 18:34 ` Konrad Rzeszutek Wilk
2011-05-05 20:48 ` Scott Garron
2011-05-05 21:06 ` Konrad Rzeszutek Wilk
2011-06-06 18:00 ` Scott Garron
2011-06-06 19:17 ` Pasi Kärkkäinen
2011-06-06 21:33 ` Scott Garron
2011-06-07 19:19 ` Konrad Rzeszutek Wilk
2011-06-08 18:25 ` Scott Garron
2011-06-08 19:29 ` Konrad Rzeszutek Wilk
2011-06-09 20:04 ` Scott Garron
2011-06-10 12:59 ` Konrad Rzeszutek Wilk
2011-06-10 16:51 ` Scott Garron
2011-06-13 22:03 ` Konrad Rzeszutek Wilk
2011-06-13 23:20 ` Scott Garron
2011-06-14 13:55 ` BUG: unable to handle kernel NULL pointer dereference at IP: [<ffffffff8105ae4c>] process_one_work+ Konrad Rzeszutek Wilk
2011-06-14 21:55 ` Scott Garron
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=20110504193550.GB24996@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-devel@sce.pridelands.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).