From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 2.6.32.27 dom0 + latest xen staging boot failure
Date: Tue, 25 Jan 2011 14:07:51 -0500 [thread overview]
Message-ID: <20110125190751.GA5723@dumpdata.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D530194305B18@orsmsx505.amr.corp.intel.com>
On Tue, Jan 25, 2011 at 10:49:52AM -0800, Kay, Allen M wrote:
> Looks like it translates to pin_pagetable_pfn. I have also attached the entire System.map file.
>
> ...
> ffffffff8100cce2 t pin_pagetable_pfn
> ffffffff8100cd1e t p2m_mid_mfn_init
Ok, then it probably is related to the issues we had with the P2M
or MFN list being incorrect... and your E820:
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009bc00 (usable)
(XEN) 000000000009bc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 0000000020000000 (usable)
(XEN) 0000000020000000 - 0000000020200000 (reserved)
(XEN) 0000000020200000 - 0000000040000000 (usable)
(XEN) 0000000040000000 - 0000000040200000 (reserved)
(XEN) 0000000040200000 - 000000009acd3000 (usable)
(XEN) 000000009acd3000 - 000000009ad67000 (reserved)
(XEN) 000000009ad67000 - 000000009afe7000 (ACPI NVS)
(XEN) 000000009afe7000 - 000000009afff000 (ACPI data)
(XEN) 000000009afff000 - 000000009b000000 (usable)
(XEN) 000000009b000000 - 000000009fa00000 (reserved)
(XEN) 00000000f8000000 - 00000000fc000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec01000 (reserved)
(XEN) 00000000fed10000 - 00000000fed14000 (reserved)
(XEN) 00000000fed18000 - 00000000fed1a000 (reserved)
(XEN) 00000000fed1c000 - 00000000fed20000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff980000 - 00000000ffc00000 (reserved)
(XEN) 00000000ffd80000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 00000001de600000 (usable)
is like swiss-cheese with the RAM regions.
What machine is this and how can I get my hands on it?
Does it boot if you have 'dom0_mem=max:512MB' (it is important
to have the 'max' there)?
next prev parent reply other threads:[~2011-01-25 19:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 2:26 2.6.32.27 dom0 + latest xen staging boot failure Kay, Allen M
2011-01-25 14:39 ` Konrad Rzeszutek Wilk
2011-01-25 18:49 ` Kay, Allen M
2011-01-25 19:07 ` Konrad Rzeszutek Wilk [this message]
2011-01-25 19:24 ` Kay, Allen M
2011-01-25 20:10 ` Konrad Rzeszutek Wilk
2011-01-25 21:26 ` Kay, Allen M
2011-01-26 2:41 ` Kay, Allen M
2011-01-26 16:14 ` Konrad Rzeszutek Wilk
2011-01-26 18:46 ` Kay, Allen M
2011-01-26 21:28 ` Konrad Rzeszutek Wilk
2011-01-26 21:53 ` Kay, Allen M
2011-01-27 1:16 ` Kay, Allen M
2011-01-27 11:59 ` Stefano Stabellini
2011-01-27 18:51 ` Kay, Allen M
2011-01-28 15:28 ` Konrad Rzeszutek Wilk
2011-01-28 15:47 ` Konrad Rzeszutek Wilk
2011-02-11 1:03 ` Kay, Allen M
2011-02-11 2:56 ` Jeremy Fitzhardinge
2011-02-11 3:07 ` Kay, Allen M
2011-02-11 17:06 ` Jeremy Fitzhardinge
2011-02-11 19:00 ` Kay, Allen M
2011-02-11 19:11 ` Kay, Allen M
2011-02-11 22:55 ` Jeremy Fitzhardinge
2011-02-15 4:28 ` Kay, Allen M
2011-02-15 14:58 ` Stefano Stabellini
2011-02-16 3:08 ` Kay, Allen M
2011-02-16 17:19 ` Stefano Stabellini
2011-02-11 14:51 ` Stefano Stabellini
2011-02-11 22:10 ` Kay, Allen M
2011-01-27 14:45 ` Konrad Rzeszutek Wilk
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=20110125190751.GA5723@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=allen.m.kay@intel.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.