From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kay, Allen M" Subject: RE: 2.6.32.27 dom0 + latest xen staging boot failure Date: Tue, 25 Jan 2011 18:41:30 -0800 Message-ID: <987664A83D2D224EAE907B061CE93D53019434A43C@orsmsx505.amr.corp.intel.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> <20110125201008.GA18756@dumpdata.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="_002_987664A83D2D224EAE907B061CE93D53019434A43Corsmsx505amrc_" Return-path: Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: xen-devel List-Id: xen-devel@lists.xenproject.org --_002_987664A83D2D224EAE907B061CE93D53019434A43Corsmsx505amrc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I noticed one of my e820 entry is not page aligned: > (XEN) 0000000000000000 - 000000000009bc00 (usable) It might be similar to the problem reported by Michael Young in attached em= ail. -----Original Message----- From: Kay, Allen M=20 Sent: Tuesday, January 25, 2011 1:26 PM To: 'Konrad Rzeszutek Wilk' Cc: xen-devel Subject: RE: [Xen-devel] 2.6.32.27 dom0 + latest xen staging boot failure 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 1= 00000 -----Original Message----- From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]=20 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 Pla= tform). >=20 > Setting 'dom0_mem=3Dmax:1024MB' worked. Booting with "dom0_mem=3Dmax:512= MB" 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 e= ntry 8000000110000463 for l1e_owner=3D0, pg_owner=3D0 (Xrror while pinning mfn 20c8c0 >=20 > Allen >=20 > -----Original Message----- > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]=20 > 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 >=20 > 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 th= e entire System.map file. > >=20 > > ... > > ffffffff8100cce2 t pin_pagetable_pfn > > ffffffff8100cd1e t p2m_mid_mfn_init >=20 > Ok, then it probably is related to the issues we had with the P2M > or MFN list being incorrect... and your E820: >=20 > (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) >=20 > is like swiss-cheese with the RAM regions. > What machine is this and how can I get my hands on it? >=20 > Does it boot if you have 'dom0_mem=3Dmax:512MB' (it is important > to have the 'max' there)? >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel --_002_987664A83D2D224EAE907B061CE93D53019434A43Corsmsx505amrc_ Content-Type: message/rfc822 Received: from orsmga001.jf.intel.com (10.7.209.18) by orsmsx604-1.jf.intel.com (10.22.226.87) with Microsoft SMTP Server id 8.2.254.0; Mon, 24 Jan 2011 06:16:50 -0800 Received: from orsmga102-1.jf.intel.com (HELO mga09.intel.com) ([10.7.208.27]) by orsmga001-1.jf.intel.com with ESMTP; 24 Jan 2011 06:16:50 -0800 Received: from lists.colo.xensource.com (HELO lists.xensource.com) ([70.42.241.110]) by mga09.intel.com with ESMTP; 24 Jan 2011 06:16:50 -0800 Received: from localhost ([127.0.0.1] helo=lists.colo.xensource.com) by lists.xensource.com with esmtp (Exim 4.43) id 1PhNDt-0000k4-Gg; Mon, 24 Jan 2011 06:16:49 -0800 Received: from spam.xensource.com ([70.42.241.90]) by lists.xensource.com with esmtp (Exim 4.43) id 1PhNDT-0000dV-Mg for xen-devel@lists.xensource.com; Mon, 24 Jan 2011 06:16:23 -0800 Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by spam.xensource.com with ESMTP id r7nUNqaAVgqvqGAj (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Mon, 24 Jan 2011 06:16:22 -0800 (PST) Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p0OEG4fI021377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 24 Jan 2011 14:16:05 GMT Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p0OEG2q3024230; Mon, 24 Jan 2011 14:16:03 GMT Received: from abhmt019.oracle.com by acsmt353.oracle.com with ESMTP id 948486871295878495; Mon, 24 Jan 2011 06:14:55 -0800 Received: from phenom (/209.6.55.207) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 24 Jan 2011 06:14:54 -0800 Received: by phenom (Postfix, from userid 1000) id 88B1B2389; Mon, 24 Jan 2011 09:14:53 -0500 (EST) From: Konrad Rzeszutek Wilk To: M A Young CC: "xen-devel@lists.xensource.com" Sender: "xen-devel-bounces@lists.xensource.com" Content-Class: urn:content-classes:message Date: Mon, 24 Jan 2011 06:14:53 -0800 Subject: Re: [Xen-devel] Crash on boot with 2.6.37-rc8-git3 Thread-Topic: [Xen-devel] Crash on boot with 2.6.37-rc8-git3 Thread-Index: Acu70VfnG/LCG77CQguQCzt1kcwz9g== Message-ID: <20110124141453.GA6511@dumpdata.com> References: <20110107212359.GA22976@dumpdata.com> <20110110184225.GB9837@dumpdata.com> <20110120192434.GA10001@dumpdata.com> <20110121152751.GA4156@dumpdata.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: orsmsx604.amr.corp.intel.com X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-TNEF-Correlator: x-ironport-av: E=Sophos;i="4.60,370,1291622400"; d="scan'208";a="852438054" x-ironport-anti-spam-filtered: true x-ironport-anti-spam-result: AsUAACIZPU1GKvFukWdsb2JhbACkewEBAQEJCwoHEQQguy+FUASEcIU8jDM x-virus-scanned: by bsmtpd at xensource.com x-beenthere: xen-devel@lists.xensource.com x-mailman-version: 2.1.5 list-id: Xen developer discussion list-post: errors-to: xen-devel-bounces@lists.xensource.com x-asg-debug-id: 1295878582-0736cf240001-8pertM x-barracuda-envelope-from: konrad@dumpdata.com x-asg-orig-subj: Re: [Xen-devel] Crash on boot with 2.6.37-rc8-git3 x-barracuda-connect: rcsinet10.oracle.com[148.87.113.121] x-barracuda-start-time: 1295878582 x-barracuda-url: http://spam.xensource.com:8000/cgi-mod/mark.cgi user-agent: Mutt/1.5.20 (2009-06-14) x-barracuda-spam-score: 0.00 x-barracuda-spam-status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=6.0 KILL_LEVEL=1000.0 tests=UNPARSEABLE_RELAY x-barracuda-spam-report: Code version 3.2, rules version 3.2.2.53307 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 UNPARSEABLE_RELAY Informational: message has unparseable relay lines x-barracuda-encrypted: AES256-SHA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Fri, Jan 21, 2011 at 09:43:34PM +0000, M A Young wrote: > On Fri, 21 Jan 2011, Konrad Rzeszutek Wilk wrote: > > >We should find out why that PTE is not being setup.... And I think > >this might be a missing entry in the MFN (thanks to Stefan Bader > >finding a bug there). Looking at your E820: > > > >[ 0.000000] Xen: 0000000000100000 - 000000003b0e2000 (usable) > > Mine is > [ 0.000000] Xen: 0000000000100000 - 00000000df66d800 (usable) > > >Your memory ends a 3b0e, which is not on a nice page boundary. > > Mine isn't on a page boundary at all! Whoa. > > >Can you try this patch (you will need to re-gigger as in 2.6.38-rc1 > >the p2m code moved out of xen/mmu.c to xen/p2m.c): > > It doesn't help, and crashes at the same place as the unaltered > kernel. My problem may not be happening in the xen code at all. From > the boot logs of one of my hack attempts that actually booted I have > > [ 0.000000] BIOS-provided physical RAM map: > [ 0.000000] Xen: 0000000000000000 - 000000000009f000 (usable) > [ 0.000000] Xen: 000000000009f000 - 0000000000100000 (reserved) > [ 0.000000] Xen: 0000000000100000 - 00000000df66d800 (usable) > [ 0.000000] Xen: 00000000df66d800 - 00000000e0000000 (reserved) > [ 0.000000] Xen: 00000000f8000000 - 00000000fc000000 (reserved) > [ 0.000000] Xen: 00000000fec00000 - 00000000fec10000 (reserved) > [ 0.000000] Xen: 00000000fed18000 - 00000000fed1c000 (reserved) > [ 0.000000] Xen: 00000000fed20000 - 00000000fed90000 (reserved) > [ 0.000000] Xen: 00000000feda0000 - 00000000feda6000 (reserved) > [ 0.000000] Xen: 00000000fee00000 - 00000000fee10000 (reserved) > [ 0.000000] Xen: 00000000ffe00000 - 0000000100000000 (reserved) > [ 0.000000] Xen: 0000000100000000 - 00000001342cb000 (usable) > [ 0.000000] NX (Execute Disable) protection: active > [ 0.000000] DMI 2.4 present. > [ 0.000000] No AGP bridge found > [ 0.000000] last_pfn =3D 0x1342cb max_arch_pfn =3D 0x400000000 > [ 0.000000] last_pfn =3D 0xdf66d max_arch_pfn =3D 0x400000000 > [ 0.000000] init_memory_mapping: 0000000000000000-00000000df66d000 > [ 0.000000] init_memory_mapping: 0000000100000000-00000001342cb000 > > The last_pfn figure above is actually one more than the last pfn > that is initialized and is obtained by right-shifting the start > memory address plus the length of the memory piece. That is fine if > the memory ends on a page boundary, but not if it doesn't because > the partial page doesn't get a pfn. Thus it is available for early We can fix how the E820 is done. Look in arch/x86/xen/setup.c for 'xen_memory_setup' function. Try to wrap make map[i].size be =3D map[i].szie & ~(PAGE_SIZE-1) that should trim off the last 2048 bytes. > allocations such as the NODE DATA chunk. Xen goes for the memory > chunk just below the 4GB mark and hits this region, bare metal > (2.6.35) starts the NODE DATA at the 4GB mark and doesn't. That should be generic and hit both cases - but I think this got fixed in 2.6.36-ish were going for the region right underneath 4GB is not done (don't remember the details, sadly). > > I am not sure if bare metal is clever enough not to try to use this > partial page, or whether it could but misses it because of how it > places the NODE_DATA (at the bottom end of a memory region rather > than the top end). If you leave the instrumentation you placed in and add 'memblock=3Ddebug' that should give you a good idea of how it does it? > > Michael Young > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --_002_987664A83D2D224EAE907B061CE93D53019434A43Corsmsx505amrc_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --_002_987664A83D2D224EAE907B061CE93D53019434A43Corsmsx505amrc_--