lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+pv=HOSysost0YYeq4pw9VKjhtQDH6MvERrYpWyisme19b7dA@mail.gmail.com>
Date:   Fri, 24 Feb 2023 13:06:37 -0500
From:   Slade Watkins <srw@...dewatkins.net>
To:     Valerio Vanni <valerio.vanni@...ind.it>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

On Fri, Feb 24, 2023 at 12:46 PM Valerio Vanni <valerio.vanni@...ind.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ