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 5ACFD81CED for ; Tue, 1 Nov 2016 09:02:29 -0700 (PDT) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id BE3ED80370; Tue, 1 Nov 2016 16:02:29 +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 8t0hNw4BmncW; Tue, 1 Nov 2016 16:02:29 +0000 (UTC) Received: from [10.0.1.120] (unknown [207.108.170.162]) (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; Tue, 1 Nov 2016 16:02:29 +0000 (UTC) To: Laszlo Ersek References: <025d38a8-b5d9-c519-3f03-59ffcbe114bf@cran.org.uk> Cc: edk2-devel@ml01.01.org From: Bruce Cran Message-ID: <5dfe6406-0efa-bdb3-d36c-156d06dfb13b@cran.org.uk> Date: Tue, 1 Nov 2016 10:02:28 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: OvmfPkg: hang in SetInterruptState with git 245cda6641ade1f1013c2d5c9c838f2706636828 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: Tue, 01 Nov 2016 16:02:29 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 10/18/2016 1:43 AM, Laszlo Ersek wrote: > On 10/18/16 02:06, Bruce Cran wrote: >> I've just built both OVMF _and_ Qemu from the latest git sources, so I >> don't know which is at fault - but I'm seeing a hang in: >> >> #0 0x000000007f9dc030 in SetInterruptState (InterruptState=104 'h') >> at /home/bcran/workspace/edk2/MdePkg/Library/BaseLib/Cpu.c:60 >> >> It's at line 60 when it calls EnableInterrupts(). > Introduced when? :) > > It's been a while since we committed anything to OvmfPkg that could > cause this. Similarly, I don't recall anything risky like this going > into UefiCpuPkg. I rebuild OVMF every few days, against current master, > and I'm not seeing this. (Just retested at aaba2a44c24e.) Just to follow up, I've just got around to re-trying it after a couple of weeks of new OpenSUSE Tumleweed kernels coming through, along with a new build of qemu and OVMF - and the problem has disappeared. -- Bruce