ryzen 5 3600x soft lockups

[Martin Gerdzhev]

I am using ubuntu 19.10 with a ryzen 5 3600x cpu and am getting soft lockups with the machine unresponsive almost on a daily basis. The only fix is a hard reset.
I have the latest amd64-microcode installed - 3.20191021.1+really3.20181128.1ubuntu2, but still continues to happen.

Description: Ubuntu 19.10
Release: 19.10

using kernel:
5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: martin 2483 F.... pulseaudio
 /dev/snd/controlC0: martin 2483 F.... pulseaudio
 /dev/snd/controlC2: martin 2483 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-12-08 (87 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 enp4s0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro acpi_enforce_resources=lax quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-40-generic N/A
 linux-backports-modules-5.3.0-40-generic N/A
 linux-firmware 1.183.4
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: eoan
Uname: Linux 5.3.0-40-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1865293/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1865293

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Martin Gerdzhev (mgerdzhev)]

apport information

[Kai-Heng Feng (kaihengfeng)]

Can you please attach `journalctl -b -1 -k` on the next boot of lockup?

[Kai-Heng Feng (kaihengfeng)]

Mar 09 03:37:22 MartoBeast kernel: Call Trace:
Mar 09 03:37:22 MartoBeast kernel: ? __cpa_addr+0x50/0x50
Mar 09 03:37:22 MartoBeast kernel: on_each_cpu+0x2d/0x60
Mar 09 03:37:22 MartoBeast kernel: cpa_flush+0x106/0x130
Mar 09 03:37:22 MartoBeast kernel: change_page_attr_set_clr+0x16d/0x200
Mar 09 03:37:22 MartoBeast kernel: set_memory_ro+0x29/0x30
Mar 09 03:37:22 MartoBeast kernel: bpf_int_jit_compile+0x2cc/0x333
Mar 09 03:37:22 MartoBeast kernel: bpf_prog_select_runtime+0xd2/0x150
Mar 09 03:37:22 MartoBeast kernel: bpf_prepare_filter+0x44c/0x4b0
Mar 09 03:37:22 MartoBeast kernel: ? hardlockup_detector_perf_cleanup.cold+0x14/0x14
Mar 09 03:37:22 MartoBeast kernel: bpf_prog_create_from_user+0xc7/0x120
Mar 09 03:37:22 MartoBeast kernel: seccomp_set_mode_filter+0x11a/0x4a0
Mar 09 03:37:22 MartoBeast kernel: do_seccomp+0x39/0x200
Mar 09 03:37:22 MartoBeast kernel: prctl_set_seccomp+0x2c/0x40
Mar 09 03:37:22 MartoBeast kernel: __x64_sys_prctl+0x52c/0x60d
Mar 09 03:37:22 MartoBeast kernel: do_syscall_64+0x5a/0x130
Mar 09 03:37:22 MartoBeast kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9

Can you test if no BPF programs are loaded?

[Martin Gerdzhev (mgerdzhev)]

How can I find out which are the BPF programs and how to disable them?

[Kai-Heng Feng (kaihengfeng)]

Mar 08 22:04:23 MartoBeast kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20190703/utaddress-204)
Mar 08 22:04:23 MartoBeast kernel: ACPI: This conflict may cause random problems and system instability

Can you please remove "acpi_enforce_resources=lax"?

[Martin Gerdzhev (mgerdzhev)]

I disabled it, but same thing.

[Martin Gerdzhev (mgerdzhev)]

It keeps happening on a daily basis. Even several times a day. Either a full lock-up where the mouse can't be moved, or sometimes the mouse can be moved, but otherwise it is completely frozen.

[Martin Gerdzhev (mgerdzhev)]

And another crash

[Martin Gerdzhev (mgerdzhev)]

So another soft lockup. It was followed by a hard lockup on the next reboot.

[ed20900 (ed20900)]

Try adding idle=nomwait processor.max_cstate=1 to the boot kernel parameters.

[Martin Gerdzhev (mgerdzhev)]

Added it. It lasted 2 days but it froze again. Mouse could be moved. After a few minutes rebooted, but nothing in the logs.

[Victor Queiroz (victorqueirozg)]

I have a Ryzen 5 3600x and I have the same issue. I get freezes where I can't move the cursor and the only fix is manually rebooting the PC. Data corruption is something that I'm already experiencing here. Not sure what to do. I'm not using Ubuntu, though. It is also reproducible on Ubuntu, although less frequent. I could reproduce on Ubuntu Desktop 20.04 Live DVD after more than an hour of watching videos and all that.

I've created a bug on kernel bug tracker because it mostly seems like a kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=208615#c1