kernels >= 6.0.6 freezing on SSD decrypt with Waydroid kernel modules

[cobalt2727]

Copy-pasted from https://www.reddit.com/r/pop_os/comments/zx04ox/6012_kernel_causes_my_laptop_to_freeze_on_the/ since I didn't get much engagement back when this first happened:

I'm currently booting this from 6.0.6, where things seem to be functioning properly. I don't think this is a repost, looked around to see if anyone else was running into it. Specs are as follows: [my neofetch]

I updated to 6.1.11 a day or two ago, and it was stuck with the same problem.

On an unrelated note, could someone add 6.0.6 back to the repo so I have a safe fallback to rely on until this is fixed? I had a scare yesterday where I had only 6.0.6 and 6.1.11 installed - and instead of setting the oldkern.conf to 6.0.6 like I had intended, systemd-boot decided it was a good idea to try booting into 6.0.12 after I had already removed it. apt install --reinstall in a chroot didn't work for the 6.0.6 kernel since it couldn't be downloaded, so I was only able to resuscitate my setup without a reinstall by borrowing .deb files for 6.0.6 from a friend's apt cache.

[cobalt2727]

update: @isolatedoctopi on https://chat.pop-os.org/ suggested running sudo kernelstub -o "splash pcie_aspm=off" - and that actually worked perfectly! any way I can help troubleshoot this so that I don't have to disable power management features to be able to properly boot my device?

[cobalt2727]

cc @mmstick

[cobalt2727]

Just updated to 6.2.0-76060200, same error.

[cobalt2727]

cc @13r0ck

[leviport]

Stop pinging people. We see the bug report. We'll respond when we have something to respond with.

[cobalt2727]

The heads-up is appreciated.

[leviport]

Just in case it's helpful, I've found that the easiest way to use older kernels is the Mainline tool: https://github.com/bkw777/mainline. This provides Ubuntu kernels, not Pop kernels, but generally the difference is small.

[cobalt2727]

Yeah, I tried experimenting a little bit with the xanmod kernel, but couldn't figure out how to get systemd-boot to show me more than just Pop's "current" kernel (which can't be uninstalled) and Pop's "oldkern" entry, which I needed to be set to 6.0.6 - so I ultimately just settled for saving a copy of the 6.0.6 deb files in a /home/ subfolder and making sure they're reinstalled every so often for good measure.

[cobalt2727]

Just updated to 6.2.0-76060200, same error.

Not sure what you guys changed, but I'm happy to report that the 6.2.0-76060200 update from a day or two ago seems to have fixed it! Thanks a ton.

[cobalt2727]

Disregard, I can at least boot but suspend/resume is busted up now. I can provide pictures later tonight when I'm at a location that lets me turn the lights down low enough to avoid doxxing myself through my laptop's very reflective touchscreen.

[cobalt2727]

@leviport Definitely wasn't expecting this. The original issue is back as of the 6.2.6-76060206 update...

[cobalt2727]

Looks like we might finally have an answer. By sheer luck I saw a post from someone else who ran into the same problem after installing Waydroid - which I've had on my laptop since before this issue popped up.

https://www.reddit.com/r/pop_os/comments/120lojm/pop_os_doesnt_boot_after_trying_to_install/

[leviport]

Ah, that makes sense. Anything that has its own DKMS modules can sometimes conflict with our kernels, since we usually keep the kernel so current for hardware enablement.

[cobalt2727]

That checks out. One question though - from one of the replies on that post:
PS: For what i understand the issue comes with the anbox-binder, some people say it isn't necessary to install it since it already comes with the system or something like that and that's what causing the issue.
Does the default Pop OS kernel have a binder module built in nowadays or something?

[leviport]

I'm not sure, sorry. I don't do any Android-related dev work.

[cobalt2727]

Would this still be considered a System76 kernel issue? To be fair, as far as I'm aware other distros aren't experiencing something like this...

[JamiKettunen]

BINDERFS appears to be enabled even on the v6.2 kernel of the 22.04-based live ISO. I think all needed Waydroid options are now enabled by default so there's no need to even try enabling them manually?