[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUlYrLG4rLwWw1ge@archlinux-ax161>
Date: Mon, 20 Sep 2021 20:59:40 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Mike Galbraith <efault@....de>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org,
marmarek@...isiblethingslab.com, Juergen Gross <jgross@...e.com>,
Mike Rapoport <rppt@...ux.ibm.com>, x86@...nel.org
Subject: Re: [tip: x86/urgent] x86/setup: Call early_reserve_memory() earlier
On Tue, Sep 21, 2021 at 05:38:40AM +0200, Borislav Petkov wrote:
> On Mon, Sep 20, 2021 at 03:48:18PM -0700, Nathan Chancellor wrote:
> > Could auto-latest get updated too so that it does not show up in -next?
> > I just spent a solid chunk of my day bisecting a boot failure on one of
> > my test boxes on -next down to this change, only to find out it was
> > already reported :/
>
> Sorry about that - commit is zapped from tip/master and tip/auto-latest.
Thank you!
> But your effort hasn't been in vain - you have a box which triggers this
> boot issue and I haven't found one yet.
>
> Can you please test on that exact test box whether the new version of
> that commit works?
>
> That one:
>
> https://lkml.kernel.org/r/20210920120421.29276-1-jgross@suse.com
>
> It would be much appreciated.
Sure thing. I tested both of my test systems and added a tested-by tag
to that thread. Glad to hear it was not in vain :)
Cheers,
Nathan
Powered by blists - more mailing lists