From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Dominic Jones <jonesd@xmission.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] v6.0.x fails to boot after updating from v5.19.x
Date: Fri, 25 Nov 2022 09:44:10 +0100 [thread overview]
Message-ID: <ea6bbb08-1784-74a0-8391-50374b80f524@leemhuis.info> (raw)
In-Reply-To: <709b163021b2608789dab55eb3f9724c.dominic@xmission.com>
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
next prev parent reply other threads:[~2022-11-25 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 1:08 [REGRESSION] v6.0.x fails to boot after updating from v5.19.x Dominic Jones
2022-11-25 8:44 ` Thorsten Leemhuis [this message]
2022-11-30 16:42 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-11-30 18:38 Dominic Jones
2022-11-25 14:59 Dominic Jones
2022-11-18 19:25 Dominic Jones
2022-10-29 23:04 Dominic Jones
2022-10-28 14:51 Dominic Jones
2022-10-28 15:06 ` Greg KH
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=ea6bbb08-1784-74a0-8391-50374b80f524@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=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).