[PATCH v1 0/2] firmware: dmi_scan: Make it work in kexec'ed kernel
Ard Biesheuvel
ardb at kernel.org
Sun Oct 17 06:31:17 PDT 2021
On Thu, 7 Oct 2021 at 09:23, Andy Shevchenko <andy.shevchenko at gmail.com> wrote:
>
> On Thu, Oct 7, 2021 at 10:20 AM Ard Biesheuvel <ardb at kernel.org> wrote:
> > On Wed, 6 Oct 2021 at 18:28, Andy Shevchenko <andy.shevchenko at gmail.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.
>
If nobody can be bothered to properly diagnose this, how important is
it, really?
More information about the kexec
mailing list