From: Dominic Jones <jonesd@xmission.com>
To: stable@vger.kernel.org
Cc: regressions@lists.linux.dev
Subject: [REGRESSION] v6.0.x fails to boot after updating from v5.19.x
Date: Fri, 28 Oct 2022 14:51:43 +0000 [thread overview]
Message-ID: <379d4e6478c763dec8baaa6009b379f1.dominic@xmission.com> (raw)
Updating the machine's kernel from v5.19.x to v6.0.x causes the machine to not
successfully boot. The machine boots successfully (and exhibits stable operation)
with version v5.19.17 and multiple earlier releases in the 5.19 line. Multiple releases
from the 6.0 line (including 6.0.0, 6.0.3, and 6.0.5), with no other changes to the
software environment, do not boot. Instead, the machine hangs after loading services
but before presenting a display manager; the machine instead shows repetitive hard
drive activity at this point and then no apparent activity.
''uname'' output for the machine successfully running v5.19.17 is:
Linux [MACHINE_NAME] 5.19.17 #1 SMP PREEMPT_DYNAMIC Mon Oct 24 13:32:29 2022 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
The machine is an OCZ Neutrino netbook, running a custom OS build largely similar to
LFS development. The kernel update uses ''make olddefconfig''.
#regzbot introduced: v5.19..v6.0
---
Dominic Jones
jonesd@xmission.com
next reply other threads:[~2022-10-28 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 14:51 Dominic Jones [this message]
2022-10-28 15:06 ` [REGRESSION] v6.0.x fails to boot after updating from v5.19.x Greg KH
2022-10-29 23:04 Dominic Jones
2022-11-18 19:25 Dominic Jones
2022-11-24 1:08 Dominic Jones
2022-11-25 8:44 ` Thorsten Leemhuis
2022-11-30 16:42 ` Greg KH
2022-11-25 14:59 Dominic Jones
2022-11-30 18:38 Dominic Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=379d4e6478c763dec8baaa6009b379f1.dominic@xmission.com \
--to=jonesd@xmission.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).