I have problems trying to use Linux distributions on my new machine, a HP Pavilion TG01-2856no. The CPU it has was released Q1 2021.

My problem is that whenever I boot a Linux distribution ISO, it appears that my CPU stalls on tasks. The most recent kernel version this has happened on is 5.13.13, with Arch Linux.

I could get journalctl logs from NixOS: https://ibb.co/album/9wMM0p

The fact that I have the same problem on multiple distributions has led me to believe that it's something to do with the kernel, but I could be wrong.

I have set Secure Boot off in my BIOS settings and the SATA emulation is set to AHCI. I have tried with RAID.

I have tried the following boot options: nomodeset, noacpi, noapic, acpi=off.

The only distributions that I have managed to get working are Devuan and Gentoo.

Secure boot isn't it.

Why do you think cpu stalls? Did you try top or other system performance monitor?

The no boot entries won't help.

Whenever I try to boot, I constantly get messages saying "rcu self-detected stalls on CPUs/tasks"

The tainted 5.10 NixOS kernel is crashing, apparently resistant to some hardware that makes up your Rocket Lake HP. What exactly happened when you tried appending nomodeset - same crash messages, or different ones, or something else? Some installers have a special failsafe boot option for difficult hardware. Have you tried any of them? You need to get the attention of someone who recognizes what to do about the specific crash messages you're getting if you can't find any distro that will boot instead of crashing. Try getting the mods to move one of your threads to the kernel forum.

I get the same errors with nomodeset, but I noticed something new. I got this ACPI error:
What distributions have the "failsafe boot option"?

Most ACPI errors are of no consequence to successfully booting.

Probably most, though not necessarily by that name. It's usually the last selection in the boot menu, whatever it's called.

I got ArchLabs and Arch to install, after using the acpi=off argument on the ISO boot. However I cannot login after this, the password has reset for both the root and normal user.

Root's password can usually be reset by booting live media and chrooting to the installation.

It still resets the password.

Maybe the problem is with the BIOS being pretty recent? The revision it currently has was released June 3rd 2021, so could it be too recent? I can't downgrade it.

The BIOS has nothing to do with root's password. Usually when someone is told to chroot to reset the root password they want to know what chroot is or how to chroot. What password is being reset? What happens to indicate the password is wrong? Did you create a BIOS password?

I probably worded it wrong.

I meant that maybe the problem with the booting and power management (ACPI) is with the BIOS, which I mentioned is recent.