Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933765Ab3CMPXH (ORCPT ); Wed, 13 Mar 2013 11:23:07 -0400 Received: from mga02.intel.com ([134.134.136.20]:4088 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932391Ab3CMPXF convert rfc822-to-8bit (ORCPT ); Wed, 13 Mar 2013 11:23:05 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,837,1355126400"; d="scan'208";a="278316038" From: "Yu, Fenghua" To: "dave@linux.vnet.ibm.com" , Tetsuo Handa , "hpa@linux.intel.com" CC: "linux-kernel@vger.kernel.org" Subject: RE: [3.9-rc1] Bug in bootup code or debug code? Thread-Topic: [3.9-rc1] Bug in bootup code or debug code? Thread-Index: AQHOH+41JMUeuBHQvESU+8AmIyoShpijvDbQ Date: Wed, 13 Mar 2013 15:22:43 +0000 Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C71220528C2DFF@ORSMSX105.amr.corp.intel.com> References: <201302060035.GCJ00057.FLHMOOFtJFSQOV@I-love.SAKURA.ne.jp><201303050015.GGI39081.LOVFtOFHQOJFSM@I-love.SAKURA.ne.jp> <201303132224.BEC60922.JStQOFMVFFOHLO@I-love.SAKURA.ne.jp> In-Reply-To: <201303132224.BEC60922.JStQOFMVFFOHLO@I-love.SAKURA.ne.jp> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2239 Lines: 70 > -----Original Message----- > From: Tetsuo Handa [mailto:penguin-kernel@I-love.SAKURA.ne.jp] > Sent: Wednesday, March 13, 2013 6:24 AM > To: Yu, Fenghua; hpa@linux.intel.com > Cc: linux-kernel@vger.kernel.org > Subject: Re: [3.9-rc1] Bug in bootup code or debug code? > > Tetsuo Handa wrote: > > Tetsuo Handa wrote: > > > Hello. > > > > > > I can boot linux-next-20130205 using kernel config at > > > http://I-love.SAKURA.ne.jp/tmp/config-3.8-rc6-next-20130205 . > > > But I get VMware's virtual machine kernel stack fault (hardware > reset) as soon > > > as kernel is loaded if CONFIG_DEBUG_VIRTUAL=y is added to the > config above. > > > > > > Since I don't get kernel stack fault if CONFIG_DEBUG_VIRTUAL=y is > added to > > > kernel config generated by "make allnoconfig", I guess something is > wrong with > > > code which is executed at very early stage of bootup. > > > > > > Any clue? > > > > > > Regards. > > > > > > > This bug is not yet fixed as of 3.9-rc1. > > Should I run git bisect? > > > > Regards. > > > > I found the location of "hardware reset" trigger. > > It is __pa_symbol(&boot_params) call, for I don't encounter "hardware > reset" if > I remove the "//" from below debug patch. > > This bug is not yet fixed as of 3.9.0-rc2-00188-g6c23cbb . > > --- a/arch/x86/kernel/microcode_intel_early.c > +++ b/arch/x86/kernel/microcode_intel_early.c > @@ -741,7 +741,9 @@ load_ucode_intel_bsp(void) > #ifdef CONFIG_X86_32 > struct boot_params *boot_params_p; > > + //while (1); > boot_params_p = (struct boot_params *)__pa_symbol(&boot_params); > + while (1); > ramdisk_image = boot_params_p->hdr.ramdisk_image; > ramdisk_size = boot_params_p->hdr.ramdisk_size; > initrd_start_early = ramdisk_image; Tetsuo and Dave, That's the place where we suspected to cause the problem. My question is: how to access global variable in linear mode in virtualization? __pa_symbol() is not a problem for native. Thanks. -Fenghua -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/