RE: [Xen-devel] 2.6.32.27 dom0 + latest xen staging boot failure

["Kay, Allen M" <allen.m.kay@xxxxxxxxx>]

I do not see any message from mm.c if dom0_mem param is used.  If dom0_mem is 
not used, then I see following error messages in the serial console log.  It is 
part of the log I sent out in my original bug report:

(XEN) mm.c:802:d0 Bad L1 flags 400000
(XEN) mm.c:1204:d0 Failure in alloc_l1_table: entry 365
(XEN) mm.c:2142:d0 Error while validating mfn 1c3eb4 (pfn 1454c) for type 100000

-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx] 
Sent: Tuesday, January 25, 2011 12:10 PM
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 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@xxxxxxxxxx] 
> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel