[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180316130156.GC5035@linux.intel.com>
Date: Fri, 16 Mar 2018 15:01:56 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Thiebaud Weksteen <tweek@...gle.com>,
Jeremy Cline <jeremy@...ine.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
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
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 <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.
Nope. You are right.
/Jarkko
Powered by blists - more mailing lists