A lot of freezes with AMD Ryzen 5 3600

this is what happened just before the last 2 hard reboots:

ago 17 17:56:52 mnj-PC /usr/lib/gdm-x-session[1289]: (EE) client bug: timer event18 debounce short: scheduled expiry is in the past (-1ms), your system is too slow
ago 17 17:57:14 mnj-PC dbus-daemon[613]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ago 17 17:58:34 mnj-PC dbus-daemon[1292]: [session uid=1000 pid=1292] Activating service name='com.gexperts.Tilix' requested by ':1.21' (uid=1000 pid=1359 comm="/usr/bin/gnome-shell " label="unconfined")
ago 17 17:58:34 mnj-PC dbus-daemon[1292]: [session uid=1000 pid=1292] Successfully activated service 'com.gexperts.Tilix'
ago 17 17:58:34 mnj-PC systemd[1270]: Started VTE child process 6015 launched by tilix process 6011.
ago 17 17:58:37 mnj-PC /usr/lib/gdm-x-session[1289]: (EE) client bug: timer event18 debounce short: scheduled expiry is in the past (-9ms), your system is too slow
-- Reboot --
ago 17 17:59:48 mnj-PC kernel: Linux version 5.7.14-1-MANJARO (builduser@LEGION) (gcc version 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PREEMPT Fri Aug 7 10:12:32 UTC 2020
--
ago 17 18:12:14 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:14 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:14 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:12:17 mnj-PC gnome-shell[1384]: setup_framebuffers: assertion 'width > 0' failed
ago 17 18:13:27 mnj-PC /usr/lib/gdm-x-session[1314]: (EE) client bug: timer event18 debounce: scheduled expiry is in the past (-3ms), your system is too slow
ago 17 18:13:27 mnj-PC /usr/lib/gdm-x-session[1314]: (EE) client bug: timer event18 debounce short: scheduled expiry is in the past (-16ms), your system is too slow
ago 17 18:13:35 mnj-PC /usr/lib/gdm-x-session[1314]: (EE) client bug: timer event18 debounce: scheduled expiry is in the past (-11ms), your system is too slow
ago 17 18:13:35 mnj-PC /usr/lib/gdm-x-session[1314]: (EE) client bug: timer event18 debounce short: scheduled expiry is in the past (-24ms), your system is too slow
ago 17 18:15:01 mnj-PC systemd[1]: Starting Cleanup of Temporary Directories...
ago 17 18:15:01 mnj-PC systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
ago 17 18:15:01 mnj-PC systemd[1]: Finished Cleanup of Temporary Directories.
ago 17 18:15:01 mnj-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:15:01 mnj-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:15:01 mnj-PC kernel: audit: type=1130 audit(1597680901.365:106): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:15:01 mnj-PC kernel: audit: type=1131 audit(1597680901.365:107): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-- Reboot --
ago 17 18:17:32 mnj-PC kernel: Linux version 5.7.14-1-MANJARO (builduser@LEGION) (gcc version 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PREEMPT Fri Aug 7 10:12:32 UTC 2020
--
ago 17 18:18:07 mnj-PC kernel: audit: type=1131 audit(1597681087.996:86): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:18:09 mnj-PC systemd[1269]: tracker-extract.service: Succeeded.
ago 17 18:18:12 mnj-PC wpa_supplicant[731]: wlp5s0: WPA: Group rekeying completed with 28:3b:82:17:1e:b8 [GTK=CCMP]
ago 17 18:18:13 mnj-PC systemd[1]: systemd-localed.service: Succeeded.
ago 17 18:18:13 mnj-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:18:13 mnj-PC kernel: audit: type=1131 audit(1597681093.390:87): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:18:13 mnj-PC systemd[1]: systemd-hostnamed.service: Succeeded.
ago 17 18:18:13 mnj-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:18:13 mnj-PC kernel: audit: type=1131 audit(1597681093.397:88): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:18:13 mnj-PC audit: BPF prog-id=13 op=UNLOAD
ago 17 18:18:13 mnj-PC audit: BPF prog-id=12 op=UNLOAD
ago 17 18:18:13 mnj-PC kernel: audit: type=1334 audit(1597681093.494:89): prog-id=13 op=UNLOAD
ago 17 18:18:13 mnj-PC kernel: audit: type=1334 audit(1597681093.494:90): prog-id=12 op=UNLOAD
ago 17 18:18:13 mnj-PC audit: BPF prog-id=10 op=UNLOAD
ago 17 18:18:13 mnj-PC audit: BPF prog-id=9 op=UNLOAD
ago 17 18:18:13 mnj-PC kernel: audit: type=1334 audit(1597681093.639:91): prog-id=10 op=UNLOAD
ago 17 18:18:13 mnj-PC kernel: audit: type=1334 audit(1597681093.639:92): prog-id=9 op=UNLOAD
ago 17 18:18:30 mnj-PC tracker-store[1732]: OK
ago 17 18:18:30 mnj-PC systemd[1269]: tracker-store.service: Succeeded.
ago 17 18:18:38 mnj-PC geoclue[1109]: Service not used for 60 seconds. Shutting down..
ago 17 18:18:38 mnj-PC systemd[1]: geoclue.service: Succeeded.
ago 17 18:18:38 mnj-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:18:38 mnj-PC kernel: audit: type=1131 audit(1597681118.014:93): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 17 18:22:44 mnj-PC /usr/lib/gdm-x-session[1287]: (EE) client bug: timer event18 debounce short: scheduled expiry is in the past (-11ms), your system is too slow
-- Reboot --
ago 17 18:23:53 mnj-PC kernel: Linux version 5.7.14-1-MANJARO (builduser@LEGION) (gcc version 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PREEMPT Fri Aug 7 10:12:32 UTC 2020

Reading your logs I suspect it might have to do with this problem:

For some things it seems a very similar problem. Even my wi-fi card disconnects often, which had never happened to me before changing mobos and CPUs. So, the solution is to change DE? Does this mutter-781835-workaround still exist? There is no trace of it

https://aur.archlinux.org/packages/mutter-performance/

I have the exact same CPU and motherboard and there is absolutely no issue with Manjaro and this hardware, I play a lot of WINE games on Steam, watch a lot of HD medias, and spend too much time on my browser, I virtually never crash (and the computer can stay up to a week sometimes before I reboot it).

I had an issue though when I bought this hardware, I had inconsistent crashes and system failures. unexplainable.

Long story short, this issue was with the RAM. The default values in the XMP profile were theoretically correct, but I had to increase just a little the tRC value in the Bios to have perfect stability. This issue was replicable with multiple Corsair 3200 memory kits (I had multiple same RAM, CPU and motherboard in hands in the past year), today I have a Crucial 3200 memory kit and the default values in the XMP profile are all the same than the Corsair one, BUT the tRC is a little higher which made this memory kit work out of the box compared to the Corsair one. I would recommend to simply check what memory you have what are the values currently applied to it, and maybe just by configuring one value you could get out of trouble soon.

Donā€™t get you hopes up, but this could simply be it. To quickly confirm an issue with the RAM, just do a ā€˜Large FFTā€™ test with Mprime (for 10 minutes to up to how much time you have to waste waiting to see if errors come, it was relatively quick in my various cases) and it should spit errors if it detects RAM related issues, then from there you know issue may simply be what Iā€™m talking about, and reconfiguring properly your RAM timings would fix it (Load XMP profile, then modify the tRC by increasing its value a little).

PS: and by the way, I use the default Bios settings only with the Power supply idle control on TYPICAL, and XMP profile loaded [and modified if default values are too tight], no messing around with other setting to have it stable (and now I even have the memory overclocked and other advanced settings but I used the computer without any ā€˜tipsā€™ from the internet for the early Ryzen issues you can find from google)

2 Likes

Thanks, I have installed it and am using it. Letā€™s see if it works, if not I will try to change DE. Meanwhile I noticed that the wi-fi card problems were related to the 5.7 kernel, it apparently works well with the 5.4 LTS kernel, but now I have some weird graphical glitches. Iā€™m starting to think the problem really is my graphics card.
Thanks so much for your help, I will update this thread if I find a solution. :slightly_smiling_face:

Thanks so much for your advice! Last night I reinstalled everything, this morning I changed the tRC values slightly (Iā€™m not sure how much they need to be increased), but I also switched from the 5.7 kernel (now default in the new iso) to the 5.4 LTS because the 5.7 gave me a lot of problems with the wifi connection and I start to think that it could be the cause of everything. Anyway now the system seems pretty stable. No freeze today. If everything goes well for a few days I will mark the problem as solved :grinning:

From memory with the XMP profile values, I have set the 3200 Corsair kitā€™s tRC from 64 to 72 in the friendsā€™ computers, if Iā€™m not mistaken, and this should be the default on my Crucial kit.

If you have done multiple things now to fix the issues, you canā€™t be sure what fixed it, but if you notice no issue, when using normally, or checking with mprime (what I would have done first actually), then itā€™s great.

Yes, you are right, now I want to try to reset the tRC values to default to understand if the problem was the kernel or the ram. Thanks again. I update this thread as soon as I have a clear result.

I have the same issue with my Thinkpad E595 running a Ryzen 5 3500U. I have tried all the latest kernels : 5.4 and up. I even tried installing Linux Mint, thinking the kernel version they are using would have that problem solved. It seemed to work without issues from a live USB for hours, so I thought it worked, but turns out it has the exact same behavior now, after I have done all of the updates. I have no issues on my Thinkpad T420 (i7-2720QM), which is also running Manjaro.

Ok, after 2 days I can confirm 100% that my problem was simply the kernel.

Hereā€™s what I did: 2 days ago I reinstalled the latest Manjaro ISO with Gnome, keeping all the default bios settings except ā€œPower supply idleā€ set to ā€œtypicalā€. So, no ram settings change and C-state active.
With the kernel 5,7 (default in this iso) I immediately had problems with the wifi card (connection that comes and goes continuously) and several freezes. I therefore installed the 5.4 LTS kernel, choosing from grub to use that. And there you have it, no freeze in 2 days and perfectly stable wifi connection. I tried again to revert to kernel 5.7 and the system freeze in 3 minutes.
So now there are no more doubts, in my case the only problem was the 5.7 kernel, perhaps due to some incompatibility with my wifi card or with this processor in particular. Anyway, my problem is solved for now.
Thanks a lot to anyone who responded and helped me to solve the problem.
:grinning: :+1:

1 Like

I use Kernel 5.7 since release so yeah I confirm it is not an issue with the Mobo or CPU with this kernel, it is surely linked to your peripherals. What if you run Kernel 5.7 without the Wifi card plugged in (to cross check things)? If you have no issue on 5.7 when the Wifi card is not in the computer then this may be an issue worth mentioning upstream for it to be fixed, imagine if at 5.4 End Of Life the issue still exists in other kernels.

Do as you wish but if it is not too difficult or too time consuming for you, I advise you to try this way you would finish the troubleshooting and could even report a bug :stuck_out_tongue:

:scream:
OMG, you hate me :sweat_smile:
Ok, Iā€™ll try in the next few days. The only problem is I have the pc a bit far from the router so I have to try it without internet. But Iā€™ll make one last try. If so, where should I report this kernel bug?

Iā€™m not even sure myself but maybe at least in the relevant (last?) update thread here, or directly at the Kernel.org webpage Reporting bugs ā€” The Linux Kernel documentation by giving all your hardware info.

1 Like

OK perfect. Letā€™s see what happens!

Good news. I have been tinkering with different configurations and I think Iā€™ve narrowed down a possible cause for the freezes to my USB-C hub (ZMUIPNG 7 in 1) which has an HDMI output. It would not boot to the desktop at all with that plugged in, using a live USB key with Manjaro. I unplugged every devices from my laptop (Thinkpad E595) and everything worked flawlessly with the kernel 5.6.15-1. I have reinstalled Manjaro and no freezes so far. Iā€™m scared of upgrading the kernel because of how stable it is right now. Iā€™ll let you guys know in a few days how it went.

It froze about 30 minutes after Iā€™ve plugged in an external monitor from the built-in HDMI port. I need to do some more testing.

It seems to be a bad RAM module. Even though I ran many tests and returned no problems. Seems to be stable with one of them. The other one does cause me issues.

Glad you found the problem. What program did you use to test the ram?

I ran Memtest86+ for at least 30 minutes without any issues. Memtest86 would just lead to a black screen when I actually started the test. I could go back, but I just couldnā€™t see anything. Apparently, itā€™s a common issue with UEFI. I actually think there is something wrong with my AC adapter now, or something with the voltage regulation inside the laptop. Iā€™ve noticed it works fine on battery and even while charging. I get issues when it gets past 97% charge. Itā€™s so weird.