Bug 196683 - Ryzen Lockups (Responses)
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
TimestampCPU
CPU Datestamp XXXX (e.g. above)
MotherboardMotherboard Chipset
Motherboard BIOS Version
Are you using memory on your Motherboard's QVL list?
Distro
Kernel (`uname -r` output)
Is `CONFIG_RCU_NOCB_CPU=y` set?
Is `rcu-nocbs` set based on available threads? (e.g. `rcu-nocbs=0-15` for a Ryzen 7)
Have you disabled C-States (C6)?
Have you explicitly disabled ASLR?
Does your system pass stress tests?
What stress tests have you used to validate hardware stability of CPU, mobo, and memory?
Is your system stable?
If your system is unstable (<=2), can you reproduce the problem consistently? If yes, how?
Have you automated synthetic load to keep core[s] busy?
Additional notes:
What version of the ATXV12 standard does your power supply support?
2
2/17/2018 14:03:43AMD Ryzen™ 7 1700X1737
ASRock Fatal1ty AB350 Gaming-ITX/ac
B3504.4YesKorora/Fedora 26
4.14.18-300.fc26.x86_64
YesYesNoNoYes
Memtest for > 24hrs, stressapptest for > 24hrs, kill-ryzen script for > 24hrs
3No
Despite my system being rock solid, if I lock my screens with gnome (which powers them off), system becomes unresponsive. Not sure if at all related to Ryzen hardware, but if I use i3lock (which keeps monitors on) instead of default gnome screen locker, then I have zero issues. That's the only "weirdness" that remains, but can have system running for months now without problems, and it's awesome.
3
2/19/2018 9:08:32AMD Ryzen™ 5 16001737 (post-RMA)ASRock AB350 Pro4B350
4.60 (AGESA PinnaclePI-AM4 1.0.0.0)
YesArchLinux4.15.3-1-ARCHYesYes
Yes, via ryzen-stabilizator (similar to zenstates.py); have also processor.max_cstate=5
YesYes
memtest86, memtest86+, mprime/prime95, occt, stressapptest
3No
Also have pcie_aspm=off. With all these workarounds, system feels stable.
4
2/17/2018 14:13:21AMD Ryzen™ 5 1600X
Can't check but post-RMA and new enough to not have segfaults
Gigabyte GA-AX370-Gaming 5
X370F20 / AGESA 1.0.0.0aYesGentoo Linux
4.15.2-00005-g982d64f675d4
YesYesNoNoYes
kill-ryzen.sh, Gentoo Linux ;-)
3No
Maybe frozen once or twice since CONFIG_RCU_NOCB_CPU but can't be certain of the cause. Was almost daily before that. Also experienced motherboard "soft-brick" this week, probably unrelated. Managed to recover it.
5
2/18/2018 3:17:26AMD Ryzen™ 7 1700X1744ASRock AB350 Pro4B3504.63 betaNoXubuntu 17.104.13.0-35-genericNoNoNoNoYeskill-ryzen.sh1
just leave the system idling for a few hours to a few days
No
The memory is not found on the QVL list but it's ECC ram (Kingston KVR21E15D8K2/16I). I've had ASLR disabled but it didn't make any difference. That's the third Ryzen 1700x in that setup. The first two suffered from the segfault bug, not the current one, but all 3 of them showed those damned idle freezes. Perhaps it's just coincidence, but the freezes always happened when the screensaver was running (Xscreensaver) - never saw a freeze within the time period until the screensaver activated
6
2/18/2018 8:54:17AMD Ryzen™ 7 1700X
Don't know, definitely produced after the segfaults under load problem.
ASUS Prime B350M-AB3503803YesArchlinux4.15.3-2-ARCHYesNo
Disabled via https://github.com/qrwteyrutiyoup/ryzen-stabilizator. Similar to zenstates.
NoYes
stress, memtest86-efi, kill-ryzen, ryzen-mame-test
3No
The only thing I've done is disable both C6 states. Before that, I never went more than two days before a complete freeze, and usually it would freeze after less than a day. I've now had 32 days of uptime without one.
7
2/18/2018 9:03:32AMD Ryzen™ 5 1600unknownASRock AB350M Pro4B3503.2NoDebian 9 "Stretch"4.14.0-0.bpo.2-amd64NoNoNoNoYesstress-ng1
I have two identical systems, functioning as servers. Overnight, after backups have finished (when most idle time occurs) they will randomly freeze.
Yes
This started happening after some months of functioning normally.

I am using ECC memory.
8
2/19/2018 2:50:11AMD Ryzen™ 5 1600MSI B350 PC MATEB350
7A34vAA (2018-01-29, AGESA 1.1.0.1)
YesUbuntu 16.044.15.2YesYesNoNoYesmake -j133No
9
2/19/2018 9:15:36
AMD Ryzen™ Threadripper™ 1950X
ASUS PRIME X399-AX3995.13YesFedora
4.13.12-300.fc27.x86_64
YesYesYes, via zenstates.pyNoYesmemtest863No
10
2/19/2018 11:34:31AMD Ryzen™ 7 1700X1728Asus PRIME X370-PROX3700902 09/08/2017YesLeap 42.34.14.20-1.1-defaultNoNoNoNoYes
kernel / gcc compile, memtest86
3No
No more system freezes since enabled optimization for daily computing. All other BIOS configuration is standard besides activation of IOMMU and SVM. RAM runs at 2400 MHz per default. CPU is RMA'd
11
2/19/2018 15:00:55AMD Ryzen™ 5 16001733ASUS PRIME B350-PLUSB3503401 Agesa 1071NoUbuntu 16.044.15.4-customYesYesNoNoYes
Memtest86+, ryzen-kill script (segfault test), kernel compilation, ffmpeg encoding
3No
12
2/20/2018 3:41:31AMD Ryzen™ 7 1800XMSI X370 Gaming Carbon ProX3707A32v19YesUbuntu4.13.0-32-genericNoNoYes, via BIOSYesYes
compilation workloads, AVX-based HPC workloads
3No
Machine assembled 1st week of April 2017, reached idle stability with AGESA Code 1.0.0.6b + C6 disabled in BIOS. "echo 0 > /proc/sys/kernel/randomize_va_space" solved my crashes under heavy load.
13
2/20/2018 4:22:32AMD Ryzen™ 5 1600ASRock AB350M Pro4B350P3.00YesFedora 274.15.3-300.fc27.x86_64NoYesYes, via BIOSNoYes
stress --cpu 12 for a hour
3No
Had random lock-ups every day before disabling C6. Now about a week without any problems.
14
2/20/2018 14:04:54AMD Ryzen™ 7 1800X
Do not know, acquired on 2017-04-19
ASRock X370 TaichiX370P3.20 (09/08/2017)No
Ubuntu 16.04.3 LTS (amd64)
4.14.15-customYesYesYes, via BIOSNoYesmemtest86+, kill-ryzen3No
RAM: 2x Kingston 9965669-019.A00G (unbuffered, ECC) on DIMMs 1 A/B; Contact: linux-ryzen-poll 4T moritz-naumann D0T com
15
2/21/2018 7:10:35AMD Ryzen™ 7 1800X1737ASUS Prime X370-ProX3703803YesFedora
4.15.3.-300.fc27.x86_64
YesYesYes, via zenstates.pyNoYes
kill-ryzen.sh (failed on pre-RMA CPU, works now) and MemTest86
1
System has frozen every 2-3 days, needing to be turned on and off. Occasionally I get "soft lockup". The system used to get into a state where the mouse still moved, but nothing else worked -- that seemed to go away when I set 'rcu-nocbs'.
No
The kernel-command-line option "processor.max_cstate=5" does not seem to do anything -- not according to zenstates.py, at least.

I arranged for "zenstates.py --c6-disable" to run in rc.local two days ago. So far, no freezing. I also received the update from kernel v4.14 to v4.15 in the last few days, though I have no reason to believe that will make a difference.

If my machine does not freeze in the next couple of weeks, I will try re-enabling C6.
16
2/23/2018 3:25:11AMD Ryzen™ 5 16001736ASUS Prime B-350m-aB3503803YesUbuntu 17.104.15.3-customYesYesNoNoYesprime3No
Everything ok after recompiling the kernel with CONFIG_RCU_NOCB_CPU=y and set rcu-nocbs=0-11 (for my ryzen 5). Before that, system stability was 1 (hangs every day)
17
2/28/2018 20:38:36AMD Ryzen™ 5 1600X
? Components bought Aug 2017, but the manufacturing week, I did not record.
Asus Prime 370 ProX3701201YesMX Linux
4.15.3-antix.1-amd64-smp
NoYesNoNoYes
Run CPU jobs 700-1100% CPU in top (like squashfs, handbrake), MEMTEST 3 full cycles, long hours with workloads from near zero to loaded.
3No
Since I added rcu_nocbs=0-11, no problems , uptime 9 days 1 hr. (updated 2.28.18)
Without that addition to grub, I would have 2 crashes per day, so far, I consider this one solved. RAM is 16G G. Skill FlareX DDR4 3200MHz with DOCP
18
2/24/2018 16:29:26AMD Ryzen™ 7 1700
Don't know, but it's RMA because of segfaults
GA-AX370 Gaming K7X370F22bNoGentoo4.15.5-gentooYesYesNoNoYes
sysbench, memtest86, Compiling with gcc (Gentoo)
3No
without CONFIG_RCU_NOCB_CPU=y and bootparameter rcu-nocbs=0-15 it reproduces the Bug after some houres idle, CPU on demand gouvernor is using
19
2/25/2018 9:52:43AMD Ryzen™ 7 17001733PRIME B350M-AB3503803YesCentOS 7 64bit
4.15.5-1.el7.elrepo.x86_64
YesYesYes, via zenstates.pyNoYesprime952No.No
It hung with the kernel 4.15.4 and bios 3803.
With the kernel 4.14 and the previous bios, I was able to get 21 days without crash. Then stopped testing. The computer was left idle for 21 days. No load.
Now with kernel 4.15.5 and bios 3803, have deactivated C6 and deactivated EPU. Also increased cpu voltage to 1.85V
20
3/4/2018 13:47:18AMD Ryzen™ 7 1800XMSI X370 Gaming PlusX3707A33v58NoDebian4.15.0-1-amd64NoNoNoNoYesstress3No
System stable since power and frequency were adjusted in the BIOS (see http://www.silence.host/node/1)
21
3/4/2018 14:50:54AMD Ryzen™ 5 2400G
ASRock AB350 Gaming-ITX/ac
B3504.5NoManjaro KDE 174.16.0-1-MANJAROYesNoNoNoNoNone1No
Using bios 4.50, sent to me from ASRock. Will test now with rcu-nocbs=0-7. Kernel 4.16-rc3 Manjaro's version works, Ubuntu 18.04's causes weird graphics.
22
3/4/2018 14:56:26AMD Ryzen™ 5 2400G
ASRock AB350 Gaming-ITX/ac
B3504.5NoManjaro KDE 174.16.0-1-MANJAROYesNoNoNoNoNone1No
Using bios 4.50, sent to me from ASRock. Will test now with rcu-nocbs=0-7. Kernel 4.16-rc3 Manjaro's version works, Ubuntu 18.04's causes weird graphics.
23
3/14/2018 11:27:52AMD Ryzen™ 5 16001738ASRock AB350 Pro4B3504.4YesArch Linux4.15.8-1-lqxYesYesNoNoYes
https://github.com/suaefar/ryzen-test
https://www.memtest86.com/
2
Yes. Let it idle for a random amount of time, wait for "CPU#X stuck" messages...
No
The PSU was produced in 2017 and is listed on the manufacturer's website as "Compliant to Intel C6/C7".
24
5/11/2018 22:18:36AMD Ryzen™ 5 2400G1831ASRock AB350M Pro4B350P4.70 02/09/2018NoUbuntu4.16.7-041607-genericNoNoNoNoYeskill-ryzen script1Just normal useNo
I don't know (only answer if you really have no way of finding this out)
25
5/22/2018 16:33:55AMD Ryzen™ 5 16001739MSI B350 TOMAHAWKB3507A34v1FYesUbuntu4.15.0-22-genericNoNoNoNoNo
no need stress test to freeze
1noNo
This bug appears when I upgrade Ubuntu from 17.10 to 18.04 (I have a nvidia graphic card)
I don't know (only answer if you really have no way of finding this out)
26
6/10/2018 10:28:04AMD Ryzen™ 5 1600
dont know. bought it in mid april 2018
Gigabyte GA-AB350-Gaming 3 (rev. 1.x)
B350F23d (F22 initially)YesGentoo4.17.0-skyNoNo
BIOS C6 package disabled (Typical idle voltage)
NoYes
rebuilding gentoo from scratch
3
enable C6 package in BIOS
No
initially chased the freezes down by using zentstates.py and disabling C6. the freezes which occured within an hour if system was almost idle didnt show up after diabling C6 via script. after investigating the BIOS and finding out that I can turn off C6 package and leave C6 for the cpu turned on (verified by zenstates.py output) I changed the BIOS switch. No occurence of random freezes since then but I am NOT running 24/7.
v2.3
27
12/22/2018 12:43:14AMD Ryzen™ 7 17001733ASUS Prime B350 PlusB3504011YesLinux Mint 19
4.18.20-041820-generic
NoNoYes, via BIOSNoYesMemtest86+ / Prime952NoNov2.3
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...