This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue Apr 23 09:35:21 2024 >From spaans Tue Feb 2 14:29:15 2016 Envelope-to: lkml@grols.ch Delivery-date: Tue, 02 Feb 2016 14:15:43 +0100 Received: from srv.grols.ch [2a00:d10:4002:1::101] by squeeze.vs19.net with IMAP (fetchmail-6.3.21) for (single-drop); Tue, 02 Feb 2016 14:29:15 +0100 (CET) Received: from vger.kernel.org ([209.132.180.67]) by home.grols.ch with esmtp (Exim 4.84) (envelope-from ) id 1aQanz-0001xS-Tr for lkml@grols.ch; Tue, 02 Feb 2016 14:15:43 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755219AbcBBNPh (ORCPT ); Tue, 2 Feb 2016 08:15:37 -0500 Received: from mga01.intel.com ([192.55.52.88]:30453 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754974AbcBBNPW convert rfc822-to-8bit (ORCPT ); Tue, 2 Feb 2016 08:15:22 -0500 Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 02 Feb 2016 05:15:23 -0800 X-ExtLoop1: 1 X-Ironport-AV: E=Sophos;i="5.22,384,1449561600"; d="scan'208";a="645841130" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by FMSMGA003.fm.intel.com with ESMTP; 02 Feb 2016 05:15:23 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.110.15) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 2 Feb 2016 05:15:22 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.172]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.117]) with mapi id 14.03.0248.002; Tue, 2 Feb 2016 21:15:14 +0800 From: "Li, Liang Z" To: David Vrabel , Andrew Cooper , "xen-devel@lists.xenproject.org" , "linux-kernel@vger.kernel.org" Cc: Daniel Kiper , Jan Beulich , Tim Deegan Subject: RE: dom0 show call trace and failed to boot on HSW-EX platform Thread-Topic: dom0 show call trace and failed to boot on HSW-EX platform Thread-Index: AdFdjJ8hHWqdvTLjTGmX+v/9sMjU6v//pMOAgAADRYD//0rMMA== Date: Tue, 2 Feb 2016 13:15:13 +0000 Message-Id: References: <56B080C7.9070704@citrix.com> <56B08385.2060009@citrix.com> In-Reply-To: <56B08385.2060009@citrix.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZGFhMzI5ZGYtNWRkOS00M2I4LTgwMTAtZGQ2NzRhZjAwOWJhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZW x-ctpclassification: CTP_IC X-Originating-IP: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org Received-SPF: none client-ip=209.132.180.67; envelope-from=linux-kernel-owner@vger.kernel.org; helo=vger.kernel.org X-Spam-Score: -6.1 X-Spam-Score-Bar: ------ X-Spam-Report: Content analysis details: (-6.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high > >> We found dom0 will crash when booing on HSW-EX server, the dom0 > >> kernel version is v4.4. By debugging I found the your patch ' > >> x86/xen: discard RAM regions above the maximum reservation' , which > the commit ID is : f5775e0b6116b7e2425ccf535243b21 caused the regression. > The debug message is listed below: > >> > ========================================================== > >> (XEN) mm.c:884:d0v14 pg_owner 0 l1e_owner 0, but real_pg_owner -1 > >> (XEN) mm.c:955:d0v14 Error getting mfn 1080000 (pfn > >> ffffffffffffffff) from L1 > >> (XEN) mm.c:1269:d0v14 Failure in alloc_l1_table: entry 0 > >> (XEN) mm.c:2175:d0v14 Error while validating mfn 188d903 (pfn > >> 17a7cc) for type > >> (XEN) mm.c:3101:d0v14 Error -16 while pinning mfn 188d903 > >> [ 33.768792] ------------[ cut here ]------------ > >> WARNING: CPU: 14 PID: 1 at arch/x86/xen/multicalls.c:129 xen_mc_ > >> [ 33.783809] Modules linked in: > >> [ 33.787304] CPU: 14 PID: 1 Comm: swapper/0 Not tainted 4.4.0 #1 > >> [ 33.793991] Hardware name: Intel Corporation BRICKLAND/BRICKLAND, > BIOS > >> [ 33.805624] 0000000000000081 ffff88017d2537c8 ffffffff812ff954 > 000000000000 > >> [ 33.813961] 0000000000000000 0000000000000081 0000000000000000 > ffff88017d25 > >> [ 33.822300] ffffffff810ca120 ffffffff81cb7f00 ffff8801879ca280 > 000000000000 > >> [ 33.830639] Call Trace: > >> [ 33.833457] [] dump_stack+0x48/0x64 > >> [ 33.839277] [] warn_slowpath_common+0x90/0xd0 > >> [ 33.846058] [] warn_slowpath_null+0x15/0x20 > >> [ 33.852659] [] xen_mc_flush+0x1c3/0x1d0 > >> [ 33.858858] [] xen_alloc_pte+0x20f/0x300 > >> [ 33.865158] [] ? update_page_count+0x45/0x60 > >> [ 33.871855] [] ? phys_pte_init+0x170/0x183 > >> [ 33.878345] [] phys_pmd_init+0x2e6/0x389 > >> [ 33.884649] [] phys_pud_init+0x2ad/0x3dc > >> [ 33.890954] [] > kernel_physical_mapping_init+0xec/0x211 > >> [ 33.898613] [] init_memory_mapping+0x17d/0x2f0 > >> [ 33.905496] [] ? > __raw_callee_save___pv_queued_spin_unloc[2 > 4;80H > >> [ 33.914516] [] ? > acpi_os_signal_semaphore+0x2e/0x32 > >> [ 33.921889] [] arch_add_memory+0x48/0xf0 > >> [ 33.928186] [] add_memory_resource+0x80/0x110 > >> [ 33.934967] [] add_memory+0x7d/0xc0 > >> [ 33.940787] [] > acpi_memory_device_add+0x14f/0x237 > > We shouldn't be adding memory based on the ACPI tables. > > David To solve this issue, what's your suggestion, simply revert? Or with a workaround? Liang