From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Sakkinen Subject: Re: Regression from efi: call get_event_log before ExitBootServices Date: Fri, 16 Mar 2018 15:01:56 +0200 Message-ID: <20180316130156.GC5035@linux.intel.com> References: <0100016206a68850-bd5c96b3-f275-46ea-98b1-1317e02a5d6e-000000@email.amazonses.com> <29c1640a-cf19-ca19-7de9-96f202edfb5a@redhat.com> <010001620bafa06b-41525407-603e-40a9-ba11-6033b2f5dcc7-000000@email.amazonses.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Paul Menzel Cc: Thiebaud Weksteen , Jeremy Cline , Ard Biesheuvel , hdegoede@redhat.com, Javier Martinez Canillas , linux-efi@vger.kernel.org, linux-integrity@vger.kernel.org, tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org List-Id: tpmdd-devel@lists.sourceforge.net On Mon, Mar 12, 2018 at 11:41:25AM +0100, Paul Menzel wrote: > 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 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. Nope. You are right. /Jarkko