[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f57f77fb-9637-e9f9-2f9c-3244ef652948@molgen.mpg.de>
Date: Mon, 12 Mar 2018 11:41:25 +0100
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Thiebaud Weksteen <tweek@...gle.com>,
Jeremy Cline <jeremy@...ine.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: hdegoede@...hat.com, Javier Martinez Canillas <javierm@...hat.com>,
linux-efi@...r.kernel.org, linux-integrity@...r.kernel.org,
tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: Regression from efi: call get_event_log before ExitBootServices
Dear Jarkko,
On 03/12/18 11:17, Jarkko Sakkinen wrote:
> On Sat, 2018-03-10 at 10:45 +0000, Thiebaud Weksteen wrote:
>> On Fri, Mar 9, 2018 at 5:54 PM Jeremy Cline <jeremy@...ine.org> wrote:
>>> and it's hanging at "memset(log_tbl, 0, sizeof(*log_tbl) + log_size);"
>>
>> Thanks. Well, it looks like the memory that is supposedly allocated is not
>> usable. I'm thinking this is a firmware bug.
>> Ard, would you agree on this assumption? Thoughts on how to proceed?
>
> Check if the BIOS is up to date?
How would that help? The no regression policy demands, that Linux
continues working on systems, where it worked before. So upgrading the
firmware is no solution, is it? Until a solution is found, the commits
should be reverted.
Kind regards,
Paul
Download attachment "smime.p7s" of type "application/pkcs7-signature" (5174 bytes)
Powered by blists - more mailing lists