MIME-Version: 1.0
References: <87f7b3f4-8586-4c10-d4f4-643ff5f0cf62@inwind.it>
In-Reply-To: <87f7b3f4-8586-4c10-d4f4-643ff5f0cf62@inwind.it>
From:   Slade Watkins <srw@sladewatkins.net>
Date:   Fri, 24 Feb 2023 13:06:37 -0500
Message-ID: <CA+pv=HOSysost0YYeq4pw9VKjhtQDH6MvERrYpWyisme19b7dA@mail.gmail.com>
Subject: Re: Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
To:     Valerio Vanni <valerio.vanni@inwind.it>
Cc:     linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Feb 24, 2023 at 12:46 PM Valerio Vanni <valerio.vanni@inwind.it> wrote:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217083
>
> I got this error after upgrading a Debian machine (x86-64) from Stretch
> to Buster. Upgrade is successful, but the next boot it crashes.

Thanks for the details. What was the last known good kernel version
that did not exhibit this issue on your system? Bisecting against that
is your best bet to try and find where a change was introduced that
might be causing this issue to occur.

>
> The machine is an Asus B360M-A with an Intel i7-8700 CPU and 16GB DDR4.
> My kernel is 4.20.17 (from kernel.org, not a distribution kernel), but I
> tried with 4.19.273 and 5.10.169 with the same .config.

Also just a quick note, since I noticed you mention it here: 4.20.y is
not supported (see kernel.org for a list of supported releases).
4.19.y and 5.10.y, however, are.

-- Slade