Ryzen 7 Lockups

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
miscous
Level 1
Level 1
Posts: 11
Joined: Mon Oct 30, 2017 2:29 am

Ryzen 7 Lockups

Post by miscous »

This is my first post! ... been using Mint since about 2010. Consider it a tribute to Mint that things just worked or I found needed answers ... for years! I moved to Germany a few months ago and recently had a local shop assemble a RYZEN system for me.

Build Details

Asus X370-A mobo
Bios 0902(19/08/2017)
Ryzen 7 1700
16Gb Corsair PC2800
Samsung 850 250 Gb ssd boot drive
WD 2TB Data drive.. blue
Asus 210(fanless) Video
Corsair 650 watt PSU

I am uncertain where to post .... but it seemed like "Other" ....

I experience random lockups. The cursor disappears ... no response form the keyboard. .... RESET! I have searched widely, changed things, and I don't know what logs to check! The lockups can be days apart. This is a great machine!. It is a "Cool and Quiet" successor to my FX8350...that didn't move to DE ..... Is this life on the RYZEN edge?

Error Messages

Code: Select all

miscous@Toll ~ $ sudo journalctl -b -p err
[sudo] password for miscous:
-- Logs begin at Mon 2017-10-30 06:53:22 CET, end at Mon 2017-10-30 06:54:35 CET
Oct 30 06:53:22 Toll kernel: core perfctr but no constraints; unknown hardware!
Oct 30 06:53:22 Toll ntpdate[917]: name server cannot be used: Temporary failure
Oct 30 06:53:23 Toll lightdm[1328]: PAM unable to dlopen(pam_kwallet.so): /lib/s
Oct 30 06:53:23 Toll lightdm[1328]: PAM adding faulty module: pam_kwallet.so
Oct 30 06:53:23 Toll lightdm[1328]: PAM unable to dlopen(pam_kwallet5.so): /lib/
Oct 30 06:53:23 Toll lightdm[1328]: PAM adding faulty module: pam_kwallet5.so
Oct 30 06:53:23 Toll NetworkManager[1092]: nm_device_get_device_type: assertion
Oct 30 06:53:23 Toll wpa_supplicant[1336]: dbus: wpa_dbus_get_object_properties:
Oct 30 06:53:23 Toll wpa_supplicant[1336]: dbus: Failed to construct signal
Oct 30 06:53:24 Toll lightdm[1427]: PAM unable to dlopen(pam_kwallet.so): /lib/s
Oct 30 06:53:24 Toll lightdm[1427]: PAM adding faulty module: pam_kwallet.so
Oct 30 06:53:24 Toll lightdm[1427]: PAM unable to dlopen(pam_kwallet5.so): /lib/
Oct 30 06:53:24 Toll lightdm[1427]: PAM adding faulty module: pam_kwallet5.so
Oct 30 06:53:46 Toll pulseaudio[2462]: [pulseaudio] pid.c: Daemon already runnin
Oct 30 06:53:46 Toll pulseaudio[2469]: [pulseaudio] pid.c: Daemon already runnin
Oct 30 06:54:11 Toll pulseaudio[2048]: [pulseaudio] bluez5-util.c: GetManagedObj
lines 1-17/17 (END)

In trying to track these things down ..... some were labeled "Solved".... but upstream .... the rest seemed not relevant to the lockups.

I would appreciate any suggestions on how to investigate the lockups.

Chuck/Miscous
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
coffee412
Level 8
Level 8
Posts: 2225
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: Ryzen 7 Lockups

Post by coffee412 »

Couple of things come to mind:

Could this processor be from the first batch that had issues? You can contact AMD and get a replacement if so. I do not know much about this issue but if you search it you can find more info. I mention that off the bat but I would also test the memory and make sure its fine. Then I would look for a bios firmware update also.

Are you running the latest kernel ?

Im running the X1800 ryzen on Asus X370 prime, 32 gigs of DDR4-and so far no issues. Im also running kernel:

Linux max 4.13.5-041305-generic #201710050600 SMP Thu Oct 5 10:02:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

coffee
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
User avatar
Pierre
Level 21
Level 21
Posts: 13204
Joined: Fri Sep 05, 2008 5:33 am
Location: Perth, AU.

Re: Ryzen 7 Lockups

Post by Pierre »

there is issues with:
- pulseaudio
- lightdm (2)
- wpa / network

start by searching for lightdm issues.

- - which version of LinuxMint are you using ?.
Image
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.
ClixTrix

Re: Ryzen 7 Lockups

Post by ClixTrix »

Read my sig-

I'm solid on the 4.10 kernel. 4.10 has the minimum level for Ryzen support. I'm on the path to test newer kernels going forward, but 4.10 is at least a good starting point.

https://www.pcworld.com/article/3176323 ... ading.html

Edit: I am tracking this bug at Ubuntu on Ryzen freezes. I had one I thought was due to a screensaver problem. Now, I'm not sure.

https://bugs.launchpad.net/ubuntu/+sour ... ug/1690085

I also want to note that I did update my BIOS to latest F5a with AGESA 1.0.0.6b after I had the freeze, so waiting for it to reoccur.
miscous
Level 1
Level 1
Posts: 11
Joined: Mon Oct 30, 2017 2:29 am

Re: Ryzen 7 Lockups

Post by miscous »

Thanks for the replies!

I have experienced lockups with both the stock 4.08 kernel and the 4.10 kernel. In addition, lockups occur with the open source as well as the recommend Nvidia driver. I also have the latest bios from Asus. I will follow happenings all all fronts to keep up to date.... running mint 18.2

On the lightdm issue, the only mention I found was from an Ubuntu forum and it recommended commenting out lines in the config file. .... haven't tried that yet as it didn't seem to directly apply to my situation. my conclusion was that was a "maybe". I will search for pulse audio and wpa issues.

Memtest is on the agenda .... I did reseat the RAM .... that was a recommendation.

Thanks again for the suggestions .....

Chuck/Miscous
User avatar
catweazel
Level 19
Level 19
Posts: 9763
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: Ryzen 7 Lockups

Post by catweazel »

miscous wrote:I have experienced lockups with both the stock 4.08 kernel and the 4.10 kernel.
Go to kernel 4.11. I run 4.13.6 lowlatency on my Ryzen 1800X rig but 4.11 should do the trick.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.
User avatar
Pjotr
Level 23
Level 23
Posts: 19927
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Ryzen 7 Lockups

Post by Pjotr »

Yesterday, kernel 4.13 (4.13.0-16.19) has become available in the official repo's. You might give that a try, as well.

Note that the minor numbering (after the 13) doesn't correspond with the upstream numbering at kernel.org; the Canonical Kernel Team uses its own minor numbering. So don't attach too much importance to the "0".

Version comparison with upstream:

Code: Select all

cat /proc/version_signature
Which tells us:

Code: Select all

pjotr@MD99587 ~ $ cat /proc/version_signature
Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
So it's a modified 4.13.4 upstream kernel.
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
ClixTrix

Re: Ryzen 7 Lockups

Post by ClixTrix »

I have the problem too. Most of my testing over the past month didn't include leaving the system in idle for a long period. Since this appears to be a pervasive problem, I wanted to see if my prior freeze was related. I was gone about 5 hours when that one happened.

I tried idling the system yesterday and got a freeze after about 4 hours of idle. Following discussion on other sites, I then disabled Global C-State Control in Bios and ran the rest of the day and overnight without a freeze. I don't show a C6 Mode Enable/Disable available in my Bios, although the manual shows it available to some processors.

This morning, I booted the system with rcu_nocbs=0-11 edit to grub. I have 6 cores/12 threads, thus the 0-11 in that option. I'm leaving the system idle and will report back if this fixes the problem. However, since the problem appears to be random, this could take some time.

Note: I can tell when it freezes by a locked clock time on screensaver.
miscous
Level 1
Level 1
Posts: 11
Joined: Mon Oct 30, 2017 2:29 am

Re: Ryzen 7 Lockups

Post by miscous »

After returning to the 4.10 kernel and the Nvidia 340 driver I have leftovers from the nouveau driver. I will try the 4.11 driver

The "solution" that I found on the lightdm message was actually for mdm.... so I didn'nt apply it.
ClixTrix

Re: Ryzen 7 Lockups

Post by ClixTrix »

I stopped the test after 8 hours and no freezes. The system sat in idle-mode with screensaver for the entire test. I double-checked that the parameter rcu_nocbs=0-11 was passed using Terminal with the following command:

Code: Select all

cat /proc/cmdline
The method to pass kernel parameters is documented here:

https://askubuntu.com/questions/19486/h ... -parameter

One odd problem I've spotted with this change is the clock in panel has stopped, even though the system isn't frozen. Checking Date from Terminal shows the correct time.

I'm restarting the test for a minimum of 12 hours / overnight and will report back in the AM tomorrow. Again, the rcu-nocbs=0-XX, where xx is the number of threads minus one for your processor, e.g. I have a six core, twelve thread processor, so I pass rcu_nocbs=0-11
miscous
Level 1
Level 1
Posts: 11
Joined: Mon Oct 30, 2017 2:29 am

Re: Ryzen 7 Lockups

Post by miscous »

This may be relevant: virtually all lockups were while I was using a browser: usually Firefox and once chromium. None that I recall were from "idle".

Memtest says all is OK, even with multithreading.

I disconnected my boot ssd and connected a conventional 320Gb hard drive and installed mint 18.2 to that ...... same errors, one lockup... I am back on the SSD with the 4.10 kernel... with no recent lockups.
mr_raider
Level 7
Level 7
Posts: 1897
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: Ryzen 7 Lockups

Post by mr_raider »

I have had zero issues with ryzen 1700x/b350 tomahawk, using kernel 4.10.

I know x370 board users have had more headaches.

Also, are you sure it's not an issue with your desktop environment or x server?

Post your full system specs with

inxi -Fxz
Image
ClixTrix

Re: Ryzen 7 Lockups

Post by ClixTrix »

Well, after 16 hours, no lockups due to idle using that parameter passed at boot.

On the frozen clock in panel, that jogged a memory and I checked some old Forum threads on that problem. Resetting the Cinnamon Panel to defaults restored the clock to normal. I'm not sure why that problem started. I did restart the system with that parameter after resetting and will check to see if it repeats. I also updated kernel from 37 to 38, so that is something else to check. More testing.....off and running.

Another cause of lockups is ASLR which can be temporarily disabled for test:

http://blog.programster.org/how-to-disable-aslr

Firefox and Chrome/Chromium use ASLR. I haven't had that problem YET, but I do see posts on various boards discussing that bug.

I assume everyone knows about the SEGFAULT bug in the Ryzens, which you can google-search and find. That takes an RMA to AMD for replacement.
User avatar
coffee412
Level 8
Level 8
Posts: 2225
Joined: Mon Nov 12, 2012 7:38 pm
Location: I dont know
Contact:

Re: Ryzen 7 Lockups

Post by coffee412 »

ClixTrix wrote:Well, after 16 hours, no lockups due to idle using that parameter passed at boot.

On the frozen clock in panel, that jogged a memory and I checked some old Forum threads on that problem. Resetting the Cinnamon Panel to defaults restored the clock to normal. I'm not sure why that problem started. I did restart the system with that parameter after resetting and will check to see if it repeats. I also updated kernel from 37 to 38, so that is something else to check. More testing.....off and running.

Another cause of lockups is ASLR which can be temporarily disabled for test:

http://blog.programster.org/how-to-disable-aslr

Firefox and Chrome/Chromium use ASLR. I haven't had that problem YET, but I do see posts on various boards discussing that bug.

I assume everyone knows about the SEGFAULT bug in the Ryzens, which you can google-search and find. That takes an RMA to AMD for replacement.
I wonder if this is a cinnamon specific issue or would Mate have the same issue? Have you ever checked? Just curious...
Ryzen x1800 Asus Prime x370-Pro 32 gigs Ram RX480 graphics
Dell PE T610, Dell PE T710
- List your hardware Profile: inxi -Fxpmrz
MeshCentral * Virtualbox * Debian * InvoiceNinja * NextCloud * Linux since kernel 2.0.36
ClixTrix

Re: Ryzen 7 Lockups

Post by ClixTrix »

I wonder if this is a cinnamon specific issue or would Mate have the same issue? Have you ever checked? Just curious...
The locked clock in Panel is Cinnamon and I might have figured-out what I did to cause that problem from my notes. I added seconds and might have goofed on the specific % sequence I coded ..... which I know can cause it to lock. I've got it running, so I'll check for recurrence.

On the general lock problems with Ryzen, those all have some specific symptoms reported on other Distro boards and at kernel.org. I think there is a lot of confusion from posters saying they did this, and this, and this, and finally got results, where the fix might be the last item tried or a specific combination. I'm reading all the boards, but following what's been tried and appears working at Ubuntu (for the obvious reasons). Some of these problems still may fall back to AMD microcode or drivers, and these patches are just workarounds. Time and testing will tell the tale.
mr_raider
Level 7
Level 7
Posts: 1897
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: Ryzen 7 Lockups

Post by mr_raider »

ClixTrix wrote:
I assume everyone knows about the SEGFAULT bug in the Ryzens, which you can google-search and find. That takes an RMA to AMD for replacement.
The segfault issue is very specific and only happens under some very precise conditions, which you are unlikely to encounter in daily useage. While AMD will RMA the processor for you, I found the downtime not worth so far.
Image
miscous
Level 1
Level 1
Posts: 11
Joined: Mon Oct 30, 2017 2:29 am

Re: Ryzen 7 Lockups

Post by miscous »

Am I certain? ..... only that lockups occurred repeatedly. This is the beginning of day 4 without problems.... Hmmmm?
My screen saver is set to blank/black screen. I don't recall any problem that I might associate with the screen saver.

I installed the 4.10 kernel with no problem .... 4.11 and 4.13 both generate multiple errors in the installation process and 4.11 doesn't boot.

System specs:

Code: Select all

System:    Host: Toll Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: MATE 1.18.0 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.2 Sonya
Machine:   Mobo: ASUSTeK model: PRIME X370-A v: Rev X.0x Bios: American Megatrends v: 0902 date: 09/08/2017
CPU:       Octa core AMD Ryzen 7 1700 Eight-Core (-HT-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 47906
           clock speeds: max: 3000 MHz 1: 1550 MHz 2: 1550 MHz 3: 1550 MHz 4: 1550 MHz 5: 1550 MHz 6: 1550 MHz
           7: 1550 MHz 8: 1550 MHz 9: 1550 MHz 10: 1550 MHz 11: 1550 MHz 12: 1550 MHz 13: 1550 MHz 14: 1550 MHz
           15: 1550 MHz 16: 1550 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 2a:00.0
           Display Server: X.Org 1.18.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on NVA8 GLX Version: 3.0 Mesa 12.0.6 Direct Rendering: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] Device 1457 driver: snd_hda_intel bus-ID: 2c:00.3
           Card-2 NVIDIA High Definition Audio Controller driver: snd_hda_intel bus-ID: 2a:00.1
           Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 28:00.0
           IF: enp40s0 state: down mac: <filter>
           Card-2: Realtek RTL8192CE PCIe Wireless Network Adapter driver: rtl8192ce port: d000 bus-ID: 29:00.0
           IF: wlp41s0 state: up mac: <filter>
Drives:    HDD Total Size: 4250.9GB (5.8% used) ID-1: /dev/sda model: Samsung_SSD_850 size: 250.1GB
           ID-2: /dev/sdb model: WDC_WD20EZRZ size: 2000.4GB ID-3: /dev/sdc model: WDC_WD20EZRZ size: 2000.4GB
Partition: ID-1: / size: 206G used: 21G (11%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 16.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: N/A mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 295 Uptime: 31 min Memory: 1007.8/16044.5MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35
User avatar
catweazel
Level 19
Level 19
Posts: 9763
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: Ryzen 7 Lockups

Post by catweazel »

miscous wrote:4.11 and 4.13 both generate multiple errors in the installation process
What is the installation process you're using?
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.
mr_raider
Level 7
Level 7
Posts: 1897
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: Ryzen 7 Lockups

Post by mr_raider »

Why are not using the nvidia proprietary driver?
Image
ClixTrix

Re: Ryzen 7 Lockups

Post by ClixTrix »

There are many posts at various boards implicating the "nouveau" video driver in Ryzen board crashes. Might try removing it for test.

Still no freeze after restarting system with kernel parm. 22 hours and climbing.

Update: After 28 hours of no idle freeze, I've added the parm into Grub Default.

Again, the parameter is:

rcu_nocbs=0-XX

where xx is the number of processor threads minus one, e.g. for a Ryzen 1600 with 6 cores and 12 threads, XX is 11.

Instructions for param add: https://askubuntu.com/questions/19486/h ... -parameter
Locked

Return to “Hardware Support”