Why some OMLx systems need mitigations=off?

I also got this warning when I checked out OpenMandriva for the first time today.
This causes programs to crash, in my case sddm borked

kernel: traps: sddm[1053] trap invalid opcode ip:7f6b0a398d65 sp:7fffa8bbc850 error:0

To fix this you have to edit your kernel command in grub by adding ‘mitigations=off’

@rbekken Welcome

Download from SouceForge?
Which ISO image please?

Thank you for the workaround. We’ll have to investigate further.

I tried the following ISO’s

SouceForge
e2c677ac34e9abe5904d5a2045fe2b4e7598fcfeb33904df41b25a47de7e5189 openmandriva.rome-24.07-plasma6.x11.x86_64.iso

abf (dot) openmandriva (dot) org/platforms/rolling/products/175/product_build_lists/3255
c765b5454fbc9bc8a2c49a7b40823e447447b67ef0ac7e4b88284b543fd5c258 OpenMandrivaLx.rolling-slim-plasma6x11.x86_64.iso

Motherboard DMI: ASUS System Product Name/ROG MAXIMUS XI HERO (WI-FI), BIOS 2004 11/02/2021

CPU: i9-9900KS

dmesg.txt (99.0 KB)
journalctl.txt (145.4 KB)

1 Like

That option is also available in grub menu. No need to edit anything, just selecting entry.

1 Like

Indeed that looks like sddm crash

Look like I was wrong about this in post #4. We are looking in to this issue.

kernel: traps: sddm[1053] trap invalid opcode ip:7f6b0a398d65 sp:7fffa8bbc850 error:0

@rbekken This needs a bug report from someone that has this issue. The issue is why some security patches like Spectre/Meltdown and others trigger this invalid opcode in OMLx systems?

mitigations=off is a boot parameter but systems with this issue are booting the problem is sddm fails and that should not be happening. At least my user level knowledge thinks it shouldn’t.