Did someone already experienced this and knows how to solve it, please?

I have this status message in retbleed under /sys/devices/system/cpu/vulnerabilities/ -
AMD mitigation “untrained return thunk” enabled and hyperthreading disabled and my kernel parameters are sat (Boot Loader) like this:

acpi=off retbleed=unret, nosmt splash=off security=apparmor

CPU Mitigation=manually

If I switch the acpi to “on” the system froze on boot after the very last line “VCN decode is enabled in VM mode and JPEGdecode is enabled in VM mode”. I can’t figured out where the problem is.

Is it hardware?

Did I have to change the CPU because is f**ked up?

The motherboard?

Or the VGA?

Have you searched for “retbleed” (?)

Might read in here to see if it helps:

(ps: a more descriptive Title is suggested for future posts :+1: )

1 Like

Yes, I’ve already searched. My CPU is a AMD gen 2 and it’s affected by it - AMD Ryzen 9 3900X Specs | TechPowerUp CPU Database

I’m going to install Fedora Workstation as secondary OS and see if things improves with CPU mitigations.

“Mitigation: untrained return thunk; SMT disabled”
AMD mitigation “untrained return thunk” enabled and hyperthreading disabled.

SPECS:

AMD Ryzen 9 3900X (stock settings, all auto)

  • Vulnerabilities:
    Gather data sampling: Not affected
    Itlb multihit: Not affected
    L1tf: Not affected
    Mds: Not affected
    Meltdown: Not affected
    Mmio stale data: Not affected
    Reg file data sampling: Not affected
    Retbleed: Mitigation; untrained return thunk; SMT disabled
    Spec rstack overflow: Mitigation; SMT disabled
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
    Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
    Spectre v2: Mitigation; Retpolines, IBPB conditional, STIBP disabled, RSB filling, PBRSB-eIBRS Not affect
    ed
    Srbds: Not affected
    Tsx async abort: Not affected

MSI B450-M Max (last firmware, 7B89v2K)

  • AGESA ComboAm4v2PI 1.2.0.B update.
  • AMD security issue patch.
  • Support new Ryzen 5000 CPU.
    RAM Kingston Fury DDR4 2x32Gb DDR4 @3200Mhz (XMP profile 1)
    PCI_E3_1: GPU Radeon Pro W5500 8Gb DDR6
    PCI_e_2: Creative Sound Blaster Z
    M.2_1 Lexar 512Gb (Main system, openSUSE Tumbleweed, EXT4 Journaled)
    SSD_1: Crucial MX500 1Tb (Second System, Windows11, NTFS)
    SSD_2: Crucial MX300 512Gb (Linux Data2, XFS Journaled)
    HDD_3: Toshiba 2Tb 7200rpm (Storage; NTFS)
    DVDRW/BR_4: Asus CD/DVD Burner

Moderators can change title - ask them.

ILL Zen 3 family have some enhancements - try to use Zen 3 CPUs

ILL VRMs on MSI B450M MORTAR MAX are rather weak, so don’t use CPUs with 12 or 16 kernels.
And you’re using AMD Ryzen 9 3900X - bad choice for that mobo.
Also use 2nd and 4th slot when using two memory modules (RTFM, man).
Post

inxi -amz

to be sure.

Message: For most reliable report, use superuser + dmidecode.

Also

https://docs.kernel.org/admin-guide/hw-vuln/srso.html

https://bbs.archlinux.org/viewtopic.php?id=288234

MSI provides AGESA ComboAm4v2PI 1.2.0.B, but the latest is AGESA ComboAm4v2PI 1.2.0.C. It is not available yet because your B450 mobo is rather old.

It performed as expected until some days ago and I’ve accomplished many things with it in the last four years. “old” is very relative here. However, CoreControl (very useful for AMD stuff) addressed me the specific bug string:

“sysret_ssattrs spectre_v1 spectre_v2 spec_store_bypass retbleed smt_rsb srso”

I’ll read this one later, instead of wasting time on wikipedia - [SOLVED]CPU speculativ store bypass prctl/seccomp / Kernel & Hardware / Arch Linux Forums

And for the record, MSI is a very ■■■■■■ company due to the fact that is gaming-centric on Microsoft products. Any MSI Bios is Windows-centered rather than dual centered. I say that in behalf of my experience with a messy Grub system when you opt for UEFI. Very differently, and better, if you opt for Legacy Bios in case of Linux necessities and dual boot. I’ve purchased an Asus B550 working/office segment for the next week.

I’m done with MSI.

This is your personal opinion which lacks facts.
In fact MSI does not prefer any OS for their Bios. This can easily be seen as you don’t need any OS installed to upgrade firmware/Bios. This is already an superior plus to many other mainboard manufacturers which needs strictly MS Windows to update. Additionally they provide a continous and long update support for their boards.

Happy owner and user of MSI Gaming motherboards which works flawlessly under Linux and which recieve continous security updates by the manufacturer…

IMHO this is causing troubles:

https://www.kernel.org/doc/html/v6.8/admin-guide/kernel-parameters.html

Try to use

mitigations=auto

or

mitigations=auto,nosmt

and delete

acpi=off

Post

inxi -aFmz

and

zypper se -si ucode

While I don’t like MSI mobos, they’re usable.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.