Asahi kernel panics after disk encryption setup?

[pattydaone]

I recently got to installing Asahi Gentoo on a Macbook of mine. I managed the install fine (this was my second time), but realized afterwork that I forgot to set up disk encryption. So I restarted, set up disk encryption as per the wiki page, and reinstalled everything. On my first reboot outside of the live environment, it loaded up perfectly fine. But on every reboot since (except one? for some reason?) I get a kernel panic with "asynchronous SError interrupt". I tried to look a little into what that means but to be honest all I could gather was "it's an arm exception. It happens when something unexpected with ram happens" not very helpful, to me at least.

I'm not sure how I'm supposed to extract logs detailing how it failed, nor am I really sure what to do from here. I went back through the disk encryption wiki page to make sure I got everything set up correctly, and I did.
The kernel version that errors, by the way, is 6.18.8. Interestingly, 6.18.15 loads the kernel fine, but can't decrypt the volume; I didn't set up dracut to be able to decrypt the volume with that kernel because it mentions you can "find kernel versions with `ls /lib/modules` and that kernel version doesn't show up in that list so I'm really not sure what to do there.

Overall, I really don't know how to go about troubleshooting this. Any help would be really appreciated. And I do want to note that prior to setting up disk encryption everything worked fine. And this is my second time setting up asahi gentoo on a mac computer, the previous go around (unencrypted) worked fine. Though, I'm not confident that disk encryption is the issue, it just seems to most obvious.

[pattydaone]

Ok so I was going to try to revert to an older version of the kernel but the ebuilds don't exist so I moved to 6.18.15 instead. It boots and seems to work and everything but it really makes me uneasy. The ebuilds for that version of the kernel were masked... I'm not too confident they're stable.
I suppose that 6.18.8 has a bug of some sort when it comes to the dm-crypt module ?

[NeddySeagoon]

pattydaone,

How were the ebuilds masked?
~arch means has not had sufficient testing to be considered stable.
Hard masked means either no testing or known broken. Here be dragons.
Someone has to be first. It may be your turn.


~arch keyworded kernels are usually safe but asahi is new to me.

Some of the ashahi devs can be found in #gentoo-arm on libera IRC.
You usually need to be registered to speak. It's a small channel and it helps keep spam down.