Re: [Regression?] Linux 5.19-rc5 gets stuck on boot, not rc4

[Thorsten Leemhuis]

On 06.07.22 10:42, torvic9@xxxxxxxxxxx wrote:
> 
>> Limonciello, Mario <mario.limonciello@xxxxxxx> hat am 05.07.2022 17:10 GMT geschrieben:
>>> -----Original Message-----
>>> From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
>>> Sent: Tuesday, July 5, 2022 11:40
>>> To: Tor Vic <torvic9@xxxxxxxxxxx>
>>> Cc: linux-kernel@xxxxxxxxxxxxxxx; platform-driver-x86@xxxxxxxxxxxxxxx;
>>> Hans de Goede <hdegoede@xxxxxxxxxx>; Jani Nikula
>>> <jani.nikula@xxxxxxxxx>
>>> Subject: Re: [Regression?] Linux 5.19-rc5 gets stuck on boot, not rc4
>>>
>>> On Tue, Jul 5, 2022 at 6:50 AM <torvic9@xxxxxxxxxxx> wrote:
>>>>
>>>> Linux 5.19-rc5 does not boot on my Kaby Lake Thinkpad.
>>>> rc3 and rc4 were still fine, so I guess something between rc4 and rc5
>>>> introduced a regression.
>>>
>>> Sounds that way.
>>>
>>>> Unfortunately, there are no errors or warning messages.
>>>> It gets stuck quite early on boot, about the time USB is initialized,
>>>> so less than 1 second into post-bootloader boot.
>>>> It then just sits there doing nothing - SysRq still works though.
>>>
>>> There aren't all that many changes in rc5, and your hardware looks
>>> *very* standard (all intel chipset, and a Samsung SM961 SSD).
>>>
>>> And with the lack of details, we'll either need a bisect:
>>>
>>>> I don't have time for a bisect, but I thought I'll let you know about
>>>> this issue, and maybe someone already has an idea.
>>>
>>> or we'll need more reports..
>>>
>>>> Some system information below. Root filesystem is f2fs.
>>>
>>> Ok, f2fs is certainly unusual, but there are no f2fs changes in rc5.
>>>
>>> There's some PM changes for i915 ("drm/i915/dgfx: Disable d3cold at
>>> gfx root port") and a couple of thinkpad-acpi platform driver updates,
>>> so I'm adding a few random people to the cc in case somebody goes
>>> "ahh..."
>>>
>>
>> If a bisect isn't possible for you the kernel command line should be pretty
>> helpful to isolate which area the problem is introduced.
>> I'd say start out with "nomodeset" on the kernel command line to prevent
>> i915 from loading.  If that fixes it, hopefully it's a small number of commits
>> to peel back like the one Linus mentioned.
> 
> Good advice!
> Using "nomodeset" makes the computer boot again.

Wild guess, I'm not involved at all in any of the following, I just
noticed it and thought it might be worth mentioning:

I heard Fedora rawhide added this patch to solve a boot problem that
sounded similar to yours:
https://patchwork.freedesktop.org/patch/489982/

See also this thread:
https://lore.kernel.org/all/fddf5ca6-77dc-88f9-c191-7de09717063c@xxxxxxxxxx/

A few config option are mentioned there that seem to have an impact.
Maybe it's worth changing those or trying that patch.

But as I said, I'm not involved, so maybe this is a bad advice.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.