[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdLLZsJnektx+n=BGvGeaogN0r=viNJpbR-au5RUURi9Q@mail.gmail.com>
Date: Thu, 7 Oct 2021 10:23:12 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Dave Young <dyoung@...hat.com>, Jean Delvare <jdelvare@...e.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Javier TiĆ” <javier.tia@...il.com>,
kexec@...ts.infradead.org, Eric Biederman <ebiederm@...ssion.com>,
linux-efi <linux-efi@...r.kernel.org>,
Matt Fleming <matt@...eblueprint.co.uk>
Subject: Re: [PATCH v1 0/2] firmware: dmi_scan: Make it work in kexec'ed kernel
On Thu, Oct 7, 2021 at 10:20 AM Ard Biesheuvel <ardb@...nel.org> wrote:
> On Wed, 6 Oct 2021 at 18:28, Andy Shevchenko <andy.shevchenko@...il.com> wrote:
> > On Mon, Jun 14, 2021 at 08:27:36PM +0300, Andy Shevchenko wrote:
> > > On Mon, Jun 14, 2021 at 08:07:33PM +0300, Andy Shevchenko wrote:
...
> > > Double checked, confirmed that it's NOT working.
> >
> > Any news here?
> >
> > Shall I resend my series?
>
> As I said before:
>
> """
> I would still prefer to get to the bottom of this before papering over
> it with command line options. If the memory gets corrupted by the
> first kernel, maybe we are not preserving it correctly in the first
> kernel.
> """
And I can't agree more, but above I asked about news, implying if
there is anything to test?
The issue is still there and it becomes a bit annoying to see my hack
patches in every tree I have been using.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists