From: Bruce Cran <bruce@cran.org.uk>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel@ml01.01.org
Subject: Re: OvmfPkg: hang in SetInterruptState with git 245cda6641ade1f1013c2d5c9c838f2706636828
Date: Tue, 1 Nov 2016 10:02:28 -0600 [thread overview]
Message-ID: <5dfe6406-0efa-bdb3-d36c-156d06dfb13b@cran.org.uk> (raw)
In-Reply-To: <b982028f-e49a-5c9f-4f62-9615578e783d@redhat.com>
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
next prev parent reply other threads:[~2016-11-01 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 0:06 OvmfPkg: hang in SetInterruptState with git 245cda6641ade1f1013c2d5c9c838f2706636828 Bruce Cran
2016-10-18 7:43 ` Laszlo Ersek
2016-11-01 16:02 ` Bruce Cran [this message]
2016-11-02 9:44 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5dfe6406-0efa-bdb3-d36c-156d06dfb13b@cran.org.uk \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox