From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel@lists.xen.org
Subject: Re: dom0 linux 3.6.0-rc4, crash due to ballooning althoug dom0_mem=X, max:X set
Date: Tue, 4 Sep 2012 12:39:03 -0400 [thread overview]
Message-ID: <20120904163903.GI23361@phenom.dumpdata.com> (raw)
In-Reply-To: <1136369816.20120904183757@eikelenboom.it>
On Tue, Sep 04, 2012 at 06:37:57PM +0200, Sander Eikelenboom wrote:
> Hi Konrad,
>
> This seems to happen only on a intel machine i'm trying to setup as a development machine (haven't seen it on my amd).
> It boots fine, i have dom0_mem=1024M,max:1024M set, the machine has 2G of mem.
>
> Dom0 and guest kernel are 3.6.0-rc4 with config:
> [*] Xen memory balloon driver
> [*] Scrub pages before returning them to system
Can you also try this patch out and provide the full log (bootup and such). Thanks!
diff --git a/drivers/xen/balloon.c b/drivers/xen/balloon.c
index 31ab82f..871a93c 100644
--- a/drivers/xen/balloon.c
+++ b/drivers/xen/balloon.c
@@ -355,8 +355,12 @@ static enum bp_state increase_reservation(unsigned long nr_pages)
BUG_ON(page == NULL);
pfn = page_to_pfn(page);
- BUG_ON(!xen_feature(XENFEAT_auto_translated_physmap) &&
- phys_to_machine_mapping_valid(pfn));
+ if (!xen_feature(XENFEAT_auto_translated_physmap)) {
+ if (phys_to_machine_mapping_valid(pfn)) {
+ printk(KERN_DEBUG "%lx is %lx!\n", pfn, get_phys_to_machine(pfn));
+ continue;
+ }
+ }
set_phys_to_machine(pfn, frame_list[i]);
@@ -572,6 +576,7 @@ static void __init balloon_add_region(unsigned long start_pfn,
*/
extra_pfn_end = min(max_pfn, start_pfn + pages);
+ printk(KERN_INFO "%s: [%lx->%lx]\n", __func__, start_pfn, extra_pfn_end);
for (pfn = start_pfn; pfn < extra_pfn_end; pfn++) {
page = pfn_to_page(pfn);
/* totalram_pages and totalhigh_pages do not
next prev parent reply other threads:[~2012-09-04 16:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 16:37 dom0 linux 3.6.0-rc4, crash due to ballooning althoug dom0_mem=X, max:X set Sander Eikelenboom
2012-09-04 16:33 ` Konrad Rzeszutek Wilk
2012-09-04 17:19 ` Sander Eikelenboom
2012-09-04 18:07 ` Ben Guthro
2012-09-04 18:22 ` Konrad Rzeszutek Wilk
2012-09-04 18:57 ` Sander Eikelenboom
2012-09-04 19:34 ` Sander Eikelenboom
2012-09-04 20:27 ` Robert Phillips
2012-09-05 14:06 ` Konrad Rzeszutek Wilk
2012-09-05 14:38 ` Sander Eikelenboom
2012-09-05 20:19 ` Konrad Rzeszutek Wilk
2012-09-05 22:52 ` Sander Eikelenboom
2012-09-06 10:57 ` Konrad Rzeszutek Wilk
2012-09-06 11:16 ` Sander Eikelenboom
2012-09-06 16:46 ` Sander Eikelenboom
2012-09-11 16:02 ` Stefano Stabellini
2012-09-12 10:28 ` Sander Eikelenboom
2012-09-12 11:28 ` Stefano Stabellini
2012-09-13 13:32 ` Konrad Rzeszutek Wilk
2012-09-13 13:42 ` Robert Phillips
2012-09-14 14:53 ` Conny Seidel
2012-09-14 17:00 ` Konrad Rzeszutek Wilk
2012-09-14 17:38 ` Conny Seidel
2012-09-17 19:14 ` Sander Eikelenboom
2012-09-17 19:23 ` Konrad Rzeszutek Wilk
2012-09-04 16:39 ` Konrad Rzeszutek Wilk [this message]
2012-09-04 18:02 ` Sander Eikelenboom
2012-09-04 17:58 ` Konrad Rzeszutek Wilk
2012-09-04 19:01 ` Sander Eikelenboom
2012-09-04 20:13 ` Sander Eikelenboom
2012-09-04 21:23 ` Sander Eikelenboom
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=20120904163903.GI23361@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.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).