Hi, Thorsten here, the Linux kernel's regression tracker. I noticed a regression report in bugzilla.kernel.org. As many (most?) kernel developers don't keep an eye on it, I decided to forward it by mail. Lino Sanfilippo, apparently it's cause by a change of yours. Note, you have to use bugzilla to reach the reporters, as I sadly[1] can not CCed them in mails like this. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217631 : > After updating to linux-6.4.1 several users of Framework Laptop > running Intel 12th gen CPUs reported that their machine fails to boot > (in my case i5-1240P). It seems it is working fine for the model > using 11th gen CPUs. See > https://community.frame.work/t/boot-and-shutdown-hangs-with-arch-linux-kernel-6-4-1-mainline-and-arch/33118 > > > > * When using TPM to unlock a LUKS volume it will wait infinitely to > start systemd-cryptsetup. When forcing a reboot, it will still wait > for this service to stop and print the following message after > waiting for some time (see attached cryptsetup_stack.jpg) * When > disabling TPM unlock, systemd-cryptsetup will start successfully and > allow to unlock the volume using the passphrase. However, after that > the boot will also wait indefinitely for systemd-pcrphase to start. > When force rebooting it will still wait for this service to stop (see > pcrphase_stack.jpg). > > I was able to boot successfully by either reverting > e644b2f498d297a928efcb7ff6f900c27f8b788e or disabling interrupts for > my model like it has been done here: > https://lore.kernel.org/linux-integrity/20230620-flo-lenovo-l590-tpm-fix-v1-1-16032a8b5a1d%40bezdeka.de/ > > DMI_MATCH(DMI_SYS_VENDOR, "Framework"), > DMI_MATCH(DMI_PRODUCT_VERSION, "A4"), See the ticket and the linked forum post for more details. [TLDR for the rest of this mail: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form.] BTW, let me use this mail to also add the report to the list of tracked regressions to ensure it's doesn't fall through the cracks: #regzbot introduced: e644b2f498d297a https://bugzilla.kernel.org/show_bug.cgi?id=217631 #regzbot title: tpm: boot problems with Framework Laptop 12th gen #regzbot ignore-activity This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply and tell me -- ideally while also telling regzbot about it, as explained by the page listed in the footer of this mail. Developers: When fixing the issue, remember to add 'Link:' tags pointing to the report (e.g. the buzgzilla ticket and maybe this mail as well, if this thread sees some discussion). See page linked in footer for details. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page. [1] because bugzilla.kernel.org tells users upon registration their "email address will never be displayed to logged out users"
