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

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: <MN0PR12MB61015A04C6E4202B2E8E08A9E2819@MN0PR12MB6101.namprd12.prod.outlook.com>
Date:   Tue, 5 Jul 2022 17:10:19 +0000
From:   "Limonciello, Mario" <Mario.Limonciello@....com>
To:     Tor Vic <torvic9@...lbox.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        Hans de Goede <hdegoede@...hat.com>,
        Jani Nikula <jani.nikula@...el.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: RE: [Regression?] Linux 5.19-rc5 gets stuck on boot, not rc4

[Public]

> -----Original Message-----
> From: Linus Torvalds <torvalds@...ux-foundation.org>
> Sent: Tuesday, July 5, 2022 11:40
> To: Tor Vic <torvic9@...lbox.org>
> Cc: linux-kernel@...r.kernel.org; platform-driver-x86@...r.kernel.org;
> Hans de Goede <hdegoede@...hat.com>; Jani Nikula
> <jani.nikula@...el.com>
> Subject: Re: [Regression?] Linux 5.19-rc5 gets stuck on boot, not rc4
> 
> On Tue, Jul 5, 2022 at 6:50 AM <torvic9@...lbox.org> 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.

For thinkpad_acpi you can try modprobe.blacklist=thinkpad_acpi.

> But otherwise I think we'll just need more reports or info to even
> start guessing.
> 
>               Linus