From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: 2.6.32.27 dom0 + latest xen staging boot failure Date: Tue, 25 Jan 2011 15:10:08 -0500 Message-ID: <20110125201008.GA18756@dumpdata.com> References: <987664A83D2D224EAE907B061CE93D5301943055D7@orsmsx505.amr.corp.intel.com> <20110125143950.GA7238@dumpdata.com> <987664A83D2D224EAE907B061CE93D530194305B18@orsmsx505.amr.corp.intel.com> <20110125190751.GA5723@dumpdata.com> <987664A83D2D224EAE907B061CE93D530194305BEA@orsmsx505.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <987664A83D2D224EAE907B061CE93D530194305BEA@orsmsx505.amr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Kay, Allen M" Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, Jan 25, 2011 at 11:24:54AM -0800, Kay, Allen M wrote: > The machine is an Intel Sandybridge Desktop SDP (Software Development Platform). > > Setting 'dom0_mem=max:1024MB' worked. Booting with "dom0_mem=max:512MB" panic'ed in mount_block_root(). OK, do you see anything on the Xen console (if you up the debug options?) I wondering if you see something akin to this: (XEN) mm.c:889:d0 Error getting mfn 110000 (pfn 5555555555555555) from L1 entry 8000000110000463 for l1e_owner=0, pg_owner=0 (Xrror while pinning mfn 20c8c0 > > Allen > > -----Original Message----- > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com] > Sent: Tuesday, January 25, 2011 11:08 AM > To: Kay, Allen M > Cc: xen-devel > Subject: Re: [Xen-devel] 2.6.32.27 dom0 + latest xen staging boot failure > > 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)? > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel