On 24.11.22 02:08, Dominic Jones wrote: >> On Fri, Oct 28, 2022 at 02:51:43PM +0000, Dominic Jones wrote: >>> 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''. >> >> Can you use 'git bisect' to find the offending change that causes this >> to happen? > > Bisection is complete. Here's what it returned. > > --- > > 3a194f3f8ad01bce00bd7174aaba1563bcc827eb is the first bad commit Many thx for this. A fix for that particular commit for recently committed to 6.0.y: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.0.y&id=bccc10be65e365ba8a3215cb702e6f57177eea07 That thus bears the question: does your problem still happen with the latest 6.0.y version? Ciao, Thorsten
