From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from muon.cran.org.uk (muon.bluestop.org [74.50.51.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 7E8131A1E04 for ; Fri, 19 Aug 2016 07:35:36 -0700 (PDT) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id C51376B4AE; Fri, 19 Aug 2016 14:35:35 +0000 (UTC) Received: from muon.cran.org.uk ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yy2sBo4-VvRZ; Fri, 19 Aug 2016 14:35:35 +0000 (UTC) Received: from [10.0.10.17] (c-67-171-116-44.hsd1.ut.comcast.net [67.171.116.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Fri, 19 Aug 2016 14:35:35 +0000 (UTC) To: "Shi, Steven" , Michael Zimmermann References: <8761c472-61cb-1968-ff1b-3bf1f04a67ad@cran.org.uk> <06C8AB66E78EE34A949939824ABE2B310338EB78@shsmsx102.ccr.corp.intel.com> Cc: edk2-devel-01 From: Bruce Cran Message-ID: <89202624-4ad5-9ff6-af36-49388985a8c5@cran.org.uk> Date: Fri, 19 Aug 2016 08:35:34 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <06C8AB66E78EE34A949939824ABE2B310338EB78@shsmsx102.ccr.corp.intel.com> Subject: Re: OVMF not booting when built with GCC5 toolset? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2016 14:35:36 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 8/18/2016 8:08 PM, Shi, Steven wrote: > I build OVMF GCC X64 image, can boot Qemu into shell with below commands. I can enter shell, reconnect -r, exit to setup, and the vga display looks good to me. What build command did you use? > > build -t GCC5 -a X64 -p OvmfPkg/OvmfPkgX64.dsc -n 5 -b DEBUG -DDEBUG_ON_SERIAL_PORT > qemu-system-x86_64 -bios OVMF.fd -serial file:serial.log -m 4096 -hda fat:. -monitor stdio -s When I built and ran it using the same commands (with the exception of adding "-vnc :0" to the qemu cmdline) I got the same problem as before, and serial.log contained just: SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78SecCoreStartupWithStack(0x30202C78 The version of gcc I'm using is: gcc version 6.1.1 20160707 [gcc-6-branch revision 238088] (SUSE Linux) -- Bruce