[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74014a7a-7d91-0854-8002-faf32d9c65e1@leemhuis.info>
Date: Sat, 1 Jul 2023 14:43:13 +0200
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Rick Edgecombe <rick.p.edgecombe@...el.com>,
Borislav Petkov <bp@...en8.de>
Subject: Re: Fwd: commit 9df9d2f0471b causes boot failure in pre-rc1 6.5
kernel
On 01.07.23 14:27, Bagas Sanjaya wrote:
> On Wed, Jun 28, 2023 at 09:06:22PM +0700, Bagas Sanjaya wrote:
>> I notice a regression report on Bugzilla [1]. Quoting from it:
> [....]
>> See Bugzilla for the full thread.
>>
>> The reporter can't provide requested dmesg due to this is early
>> boot failure, unfortunately.
>>
>> Nevertheless, this regression has already been taken care of on
>> Bugzilla, but to ensure it is tracked and doesn't get fallen through
>> cracks unnoticed, I'm adding it to regzbot:
>>
>> #regzbot introduced: 9df9d2f0471b https://bugzilla.kernel.org/show_bug.cgi?id=217602
>> #regzbot title: early arch_cpu_finalize_init() cause immediate boot failure
>
> #regzbot fix: 0303c9729afc40
Bagas, FWIW, there was no need for this at all. Regzbot would have
noticed that patch automatically due to the "Link:
https://bugzilla.kernel.org/show_bug.cgi?id=217602" in the patch
description (thx for this, tglx) once it landed in next or mainline
(just like it noticed
https://lore.kernel.org/lkml/168813193932.404.2885732890333911092.tip-bot2@tip-bot2/
earlier).
Ciao, Thorsten
Powered by blists - more mailing lists