Arch Linux

Description:
After updating to linux-6.4.1 several users of Framework Laptop running Intel 12th gen CPUs [reported](https://community.frame.work/t/boot-and-shutdown-hangs-with-arch-linux-kernel-6-4-1-mainline-and-arch/33118) that their machine fails to boot. It seems it is working fine for the model using 11th gen CPUs.

* 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 bisected the issue and it is caused by commit [e644b2f498d297a928efcb7ff6f900c27f8b788e](https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux/+/e644b2f498d297a928efcb7ff6f900c27f8b788e%5E%21/#F0)

Building the kernel after `git checkout v6.4 && git revert e644b2f498d297a928efcb7ff6f900c27f8b788e` results in a kernel which is booting fine for me.


Additional info:
* Tested package versions: linux-6.4.1.arch1-1 & linux-xanmod-6.4.0-1 & linux-xanmod-6.4.0-2 & linux-xanmod-6.4.1-1
* Kernel config attached
* I found [this issue](https://www.reddit.com/r/archlinux/comments/yshlbf/tpm2_pcr_barrier_initialization_blocking_boot/) and the related links. I am not using tpm2-abrmd and it seems it was resolved in systemd some time ago.

Steps to reproduce:
* Install the most recent kernel on a Framework Laptop 12th generation (in my case i5-1240P)
* Try to boot