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 8E8D41A1E04 for ; Fri, 19 Aug 2016 07:46:55 -0700 (PDT) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 792CF6B4CE; Fri, 19 Aug 2016 14:46:54 +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 nInkAEaruxit; Fri, 19 Aug 2016 14:46:53 +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:46:53 +0000 (UTC) To: "Shi, Steven" , Michael Zimmermann References: <8761c472-61cb-1968-ff1b-3bf1f04a67ad@cran.org.uk> <06C8AB66E78EE34A949939824ABE2B310338EB78@shsmsx102.ccr.corp.intel.com> <89202624-4ad5-9ff6-af36-49388985a8c5@cran.org.uk> Cc: edk2-devel-01 From: Bruce Cran Message-ID: <13f9450a-ac68-dca0-148e-ad9baf8380b6@cran.org.uk> Date: Fri, 19 Aug 2016 08:46:53 -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: <89202624-4ad5-9ff6-af36-49388985a8c5@cran.org.uk> 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:46:55 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 8/19/2016 8:35 AM, Bruce Cran wrote: > 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 > Sorry, I'd added -O0 to the debug build flags to let me better debug code. With that removed, I now get the following in serial.log: SecCoreStartupWithStack(0x0, 0x0) Register PPI Notify: Install PPI: Install PPI: The 8519680th FV start address is 0x00000810248, size is 0xFFFD13C4, handle is 0x827F01 Register PPI Notify: Register PPI Notify: Install PPI: Install PPI: Loading PEIM at 0x00000000000 EntryPoint=0x00000000000 SecCoreStartupWithStack(0xFFFFFFFF, 0xAE569B3A) Register PPI Notify: SecCoreStartupWithStack(0xFFFFFFFF, 0xAE569B3A) Register PPI Notify: SecCoreStartupWithStack(0xFFFFFFFF, 0xAE569B3A) Register PPI Notify: SecCoreStartupWithStack(0xFFFFFFFF, 0xAE569B3A) Register PPI Notify: SecCoreStartupWithStack(0xFFFFFFFF, 0xAE569B3A) Register PPI Notify: Those last 2 lines repeat about 100 times. -- Bruce