-Article edited by kc_admin.
For the past year, I’ve been planning to build a new desktop PC. AMD’s March introduction of Ryzen’s new architecture piqued my interest. Although it doesn’t have the fastest single core performance, having 8 cores does make for an engaging workstation. Being the cautious type, I’ve followed the introduction and Google searched “amd ryzen problems” frequently to gain insight as to how ready the platform was for prime time. The main issues of discussion among early adopters:
- Memory compatibility issues (mainly the inability in running at advertised speeds of the DIMMs)
- Linux:
- during heavy gcc compiling a segfault may occur. This is now a very well documented issue that AMD has acknowledged and has been accepting RMA’s to replace those processors affected.
- Reboots during idle time.
- MCE errors.
- Windows:
- Random freezes.
- Problems installing Windows 10.
Seven months have passed since the initial release and many updates have been released to address many of these issues. I’ve chosen to purchase a Ryzen 7 1800x system and since it’s not time critical to get it up and running as my main desktop system, I’ve decided to experiment with it to determine if these issues have been resolved and if not, investigate viable workarounds.
General Test Plan
- Assemble hardware
- Ensure latest BIOS version is installed.
- Run memtest86 for 48 hours.
- Run Prime95 for 6 hours.
- Install Ubuntu Mate 16.04 with HWE kernel. (1 to 2 week test):
- Segfault issues.
- MCE errors.
- Reboots during idle time.
- Install latest version of Vmware player and test for stability.
- Install Windows 10 (Latest version obtainable from Microsoft’s site.) (1 to 2 week test)
- Prepare it as my new desktop and observe for random freezes, etc.
- Install latest version of Vmware player and test for stability.
Over the next few weeks, I’ll be detailing the build, the tests, and the results on these pages. Up first, let’s review the build!
Parts BOM:
- Ryzen 7 1800x
- Asus Prime X370 Motherboard
- FlareX F4-2400C15Q-64GFXR 64GB of RAM (Certified by G.Skill to work with the Asus Prime X370 Motherboard) CL15-15-15-39 1.2v
- Samsung 960 EVO 1TB PCIe NVME drive
- Seasonic Prime 750 Titanium Power Supply
- Cooler Master HAV XB EVO Case
- Pioneer BDR-209DBK Internal Bluray Drive
- Acer Predator XB1 XB271HU bmipr QHD 27inch IPS monitor
- Old Video Card (Nvidia GS840) until I select a new one.
As of today, 10/15/2017, I’ve received my complete order from New Egg and am waiting for the final shipment from Amazon.
The Amazon order arrived on 10/16/2017 and I commenced with building the system on 10/20/2017.
The Processor:
As you can see it was manufactured in 2017, week 19 (UA 1719SUT.) That puts it in the week of May 8th.
The Memory:
Very recent manufacture date: September 2017. Four of these make up the 64GB I'm installing.
The Build.
The build itself went smoothly. After realizing that the rear drive bays in the Cooler Master case are only accessible when the motherboard is out, I decided to add an Icy Dock 4x2.5 drive bay that fits into the externally accessible 5.25 inch bay. I also picked up a bunch of Cooler Master fans and 4 sata cables to get everything hooked up. Once it was all assembled, I moved it into the bedroom and connected it to a 46inch TV to begin testing. It worked the first time I turned it on. After reviewing the BIOS and making sure it recognized all of the installed components, I booted Memtest86 from USB and began the memory test. After almost 27 hours, the test concluded with 0 errors.
I felt this was a a great start and then proceeded to install Ubuntu Mate 16.04.3 onto a spare Samsung 840 ssd that I placed into the Icy Dock. Install went fine and then I installed MPrime for a 6 hour run. Here's a screen shot of the test in progress:
You can see in the window on the right that all cores were running at 3.6GHZ during the test. On the bottom you can see two sensors, fan speed and CPU temperature. Sensors-detect wasn't able to read the motherboard's sensors and the default K10 readings aren't accurate. On startup and idle it indicates 131 degrees F. I read that later Kernels (Ubuntu 16.04.3 currently is using the 4.10 line) will better support Ryzen and the current crop of motherboards better. After about 6 hours I ended the test with no errors.
It looks to me that I have a rock solid system!
Sunday October 22nd to the 23rd, 2017.
For me, this is a very important question. During compiling with GCC, is the system stable? I read a lot about it on AMD's Community Forum and I was wondering how widespread the issue is and how likely it would be for a person building a new system now, 7 months after introduction. The easiest way to test this condition is with Marc Suaefar's script located on his Github Page. It's an easy download and execution. I did so and here's a copy of my terminal session:
Extract GCC sources
Download prerequisites
2017-10-22 18:17:43 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/gmp-6.1.0.tar.bz2 [2383840] -> "./gmp-6.1.0.tar.bz2" [1]
2017-10-22 18:17:44 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/mpfr-3.1.4.tar.bz2 [1279284] -> "./mpfr-3.1.4.tar.bz2" [1]
2017-10-22 18:17:45 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/mpc-1.0.3.tar.gz [669925] -> "./mpc-1.0.3.tar.gz" [1]
2017-10-22 18:17:47 URL: ftp://gcc.gnu.org/pub/gcc/infrastructure/isl-0.16.1.tar.bz2 [1626446] -> "./isl-0.16.1.tar.bz2" [1]
gmp-6.1.0.tar.bz2: OK
mpfr-3.1.4.tar.bz2: OK
mpc-1.0.3.tar.gz: OK
isl-0.16.1.tar.bz2: OK
All prerequisites downloaded successfully.
cat /proc/cpuinfo | grep -i -E "(model name|microcode)"
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
model name : AMD Ryzen 7 1800X Eight-Core Processor
microcode : 0x8001129
sudo dmidecode -t memory | grep -i -E "(rank|speed|part)" | grep -v -i unknown
Speed: 2400 MHz
Part Number: F4-2400C15-16GFXR
Rank: 2
Configured Clock Speed: 1200 MHz
Speed: 2400 MHz
Part Number: F4-2400C15-16GFXR
Rank: 2
Configured Clock Speed: 1200 MHz
Speed: 2400 MHz
Part Number: F4-2400C15-16GFXR
Rank: 2
Configured Clock Speed: 1200 MHz
Speed: 2400 MHz
Part Number: F4-2400C15-16GFXR
Rank: 2
Configured Clock Speed: 1200 MHz
uname -a
Linux ryzen7 4.10.0-37-generic #41~16.04.1-Ubuntu SMP Fri Oct 6 22:42:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
cat /proc/sys/kernel/randomize_va_space
2
/ /mnt/ramdisk/workdir
/mnt/ramdisk/workdir
Using 16 parallel processes
[KERN] -- Logs begin at Sun 2017-10-22 11:10:45 PDT. --
[KERN] Oct 22 17:56:44 ryzen7 kernel: nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1
[KERN] Oct 22 18:12:53 ryzen7 kernel: zram: Added device: zram0
[KERN] Oct 22 18:12:53 ryzen7 kernel: zram0: detected capacity change from 0 to 68719476736
[KERN] Oct 22 18:12:54 ryzen7 kernel: EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: discard
[KERN] Oct 22 18:13:22 ryzen7 kernel: zram: Cannot change disksize for initialized device
[loop-0] Sun Oct 22 18:17:48 PDT 2017 start 0
[loop-1] Sun Oct 22 18:17:49 PDT 2017 start 0
[loop-2] Sun Oct 22 18:17:50 PDT 2017 start 0
[loop-3] Sun Oct 22 18:17:51 PDT 2017 start 0
[loop-4] Sun Oct 22 18:17:52 PDT 2017 start 0
[loop-5] Sun Oct 22 18:17:53 PDT 2017 start 0
[loop-6] Sun Oct 22 18:17:54 PDT 2017 start 0
[loop-7] Sun Oct 22 18:17:55 PDT 2017 start 0
[loop-8] Sun Oct 22 18:17:56 PDT 2017 start 0
[loop-9] Sun Oct 22 18:17:57 PDT 2017 start 0
[loop-10] Sun Oct 22 18:17:58 PDT 2017 start 0
[loop-11] Sun Oct 22 18:17:59 PDT 2017 start 0
[loop-12] Sun Oct 22 18:18:00 PDT 2017 start 0
[loop-13] Sun Oct 22 18:18:01 PDT 2017 start 0
[loop-14] Sun Oct 22 18:18:02 PDT 2017 start 0
[loop-15] Sun Oct 22 18:18:03 PDT 2017 start 0
[KERN] Oct 22 18:18:25 ryzen7 kernel: show_signal_msg: 4 callbacks suppressed
[KERN] Oct 22 18:18:25 ryzen7 kernel: bash[21819]: segfault at 40e3d7c8 ip 0000000000485d57 sp 00007fff02d6f640 error 4 in bash[400000+f4000]
[loop-4] Sun Oct 22 18:18:26 PDT 2017 build failed
[loop-4] TIME TO FAIL: 38 s
[KERN] Oct 22 18:18:32 ryzen7 kernel: nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1
[loop-1] Sun Oct 22 18:19:30 PDT 2017 build failed
[loop-1] TIME TO FAIL: 102 s
[KERN] Oct 22 18:19:30 ryzen7 kernel: bash[24648]: segfault at af5908 ip 000000000041d989 sp 00007ffe00c431b8 error 6 in bash[400000+f4000]
[loop-10] Sun Oct 22 18:20:03 PDT 2017 build failed
[loop-10] TIME TO FAIL: 135 s
[KERN] Oct 22 18:20:03 ryzen7 kernel: bash[4672]: segfault at eeff89 ip 00007fac97d8d694 sp 00007ffe60001590 error 6 in libc-2.23.so[7fac97c28000+1c0000]
[loop-12] Sun Oct 22 18:51:47 PDT 2017 build failed
[loop-12] TIME TO FAIL: 2039 s
[KERN] Oct 22 18:51:47 ryzen7 kernel: traps: bash[13646] trap invalid opcode ip:48db90 sp:7ffeb8c397e8 error:0
[KERN] Oct 22 18:51:47 ryzen7 kernel: in bash[400000+f4000]
[loop-2] Sun Oct 22 20:46:00 PDT 2017 build failed
[loop-2] TIME TO FAIL: 8892 s
[KERN] Oct 22 20:46:00 ryzen7 kernel: traps: bash[10023] trap invalid opcode ip:41d98e sp:7ffcbeb2f6a8 error:0
[KERN] Oct 22 20:46:00 ryzen7 kernel: in bash[400000+f4000]
[loop-3] Sun Oct 22 21:14:01 PDT 2017 build failed
[loop-3] TIME TO FAIL: 10573 s
[loop-15] Sun Oct 22 21:15:59 PDT 2017 build failed
[loop-15] TIME TO FAIL: 10691 s
[KERN] Oct 22 21:15:59 ryzen7 kernel: bash[22025]: segfault at 39 ip 00000000004b9dec sp 00007ffd937de718 error 4 in bash[400000+f4000]
[KERN] Oct 22 21:18:39 ryzen7 kernel: nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1
[loop-7] Sun Oct 22 21:21:38 PDT 2017 start 1
[loop-5] Sun Oct 22 21:21:39 PDT 2017 start 1
[loop-8] Sun Oct 22 21:21:46 PDT 2017 start 1
[loop-6] Sun Oct 22 21:21:46 PDT 2017 start 1
[loop-9] Sun Oct 22 21:21:53 PDT 2017 start 1
[loop-0] Sun Oct 22 21:21:53 PDT 2017 start 1
[loop-13] Sun Oct 22 21:22:02 PDT 2017 start 1
[loop-11] Sun Oct 22 21:22:05 PDT 2017 start 1
[loop-5] Sun Oct 22 21:22:11 PDT 2017 build failed
[loop-5] TIME TO FAIL: 11063 s
[KERN] Oct 22 21:22:11 ryzen7 kernel: bash[32615]: segfault at 0 ip 00007f27bc6d4746 sp 00007fff7504e040 error 4 in libc-2.23.so[7f27bc649000+1c0000]
[loop-14] Sun Oct 22 21:22:14 PDT 2017 start 1
^C
me@ryzen7:~/Downloads$ [KERN] Oct 22 21:34:22 ryzen7 kernel: nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1
To my surprise, it only took 39 seconds for the first segfault with the second appearing within 102 seconds. After recovering from my initial shock, I decided to run a few more tests. The first was to do a simple kernel compile in 16.04.3 with 16 threads and the second was to do another run with Marc's test, but this time with only 4 concurrent compiles with each taking 4 threads. The single kernel compile completed without issue (albeit a short test) and the 4x4 test resulted in a segfault within the first 5 minutes. Since Ubuntu 16.04.3 is using the 4.10 kernel, and Ubuntu 17.10 was just released using the 4.12 kernel line, for completeness, I decided to upgrade to 17.10 and perform Marc's test one more time. The upgrade went fine, but the test failed with segfaults within the first 2 minutes - killing the terminal window in which the test was running.
I decided to table this issue for now and continue testing.
Is Linux stable on Ryzen during idle times? Idle times meaning - not actively running any apps. As far as tests go, this one is pretty easy to execute; all it takes is time. To conduct this test, I started a VNC session to the machine - something I could connect to from time to time without having to physically be at the computer. This test ran for three days with the third day ending in a strange almost hung state. The system would respond to pings, allow me to ssh to it and type in a username and password, but never respond with a command prompt. I was not able to interact with the system with connected keyboard or mouse either. After rebooting, I took a look in /var/log/syslog and found the following:
Oct 26 07:35:03 ryzen7 anacron[7524]: Job `cron.daily' terminated Oct 26 07:35:03 ryzen7 anacron[7524]: Normal exit (1 job run) Oct 26 07:44:06 ryzen7 kernel: [221161.641751] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 07:44:06 ryzen7 kernel: [221161.762758] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:06:42 ryzen7 kernel: [222517.707128] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:06:42 ryzen7 kernel: [222517.827954] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:14:08 ryzen7 kernel: [222963.730150] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:14:08 ryzen7 kernel: [222963.845966] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:17:01 ryzen7 CRON[16270]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Oct 26 08:23:04 ryzen7 kernel: [223499.756719] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:23:04 ryzen7 kernel: [223499.877604] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:28:07 ryzen7 kernel: [223802.776797] nouveau 0000:28:00.0: DRM: DDC responded, but no EDID for DVI-I-1 Oct 26 08:31:13 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:31:13 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:31:13 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:31:23 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:31:23 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:31:23 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:31:33 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:31:33 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:31:33 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:31:43 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:31:43 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:31:43 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:31:53 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:31:53 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:31:53 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:32:03 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:32:03 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:32:03 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:32:06 ryzen7 kernel: [224041.662913] INFO: rcu_sched detected stalls on CPUs/tasks: Oct 26 08:32:06 ryzen7 kernel: [224041.662924] 0-...: (0 ticks this GP) idle=b9c/0/0 softirq=3521708/3521708 fqs=0 Oct 26 08:32:06 ryzen7 kernel: [224041.662928] 1-...: (31 GPs behind) idle=3e8/0/0 softirq=2327060/2327060 fqs=0 Oct 26 08:32:06 ryzen7 kernel: [224041.662932] 6-...: (0 ticks this GP) idle=0c4/0/0 softirq=3437103/3437103 fqs=0 Oct 26 08:32:06 ryzen7 kernel: [224041.662935] 7-...: (19 GPs behind) idle=498/0/0 softirq=2336767/2336767 fqs=0 Oct 26 08:32:06 ryzen7 kernel: [224041.662938] 12-...: (3 GPs behind) idle=ca4/0/0 softirq=2646584/2646584 fqs=0 Oct 26 08:32:06 ryzen7 kernel: [224041.662941] 13-...: (73 GPs behind) idle=b82/0/0 softirq=2110429/2110430 fqs=0 Oct 26 08:32:06 ryzen7 kernel: [224041.662943] 15-...: (77 GPs behind) idle=cb2/0/0 softirq=2279584/2279584 fqs=0 Oct 26 08:32:06 ryzen7 kernel: [224041.662944] (detected by 2, t=15202 jiffies, g=3043662, c=3043661, q=1125) Oct 26 08:32:06 ryzen7 kernel: [224041.662947] Task dump for CPU 0: Oct 26 08:32:06 ryzen7 kernel: [224041.662948] swapper/0 R running task 0 0 0 0x00000008 Oct 26 08:32:06 ryzen7 kernel: [224041.662950] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.662957] ? cpuidle_enter_state+0xfa/0x2d0 Oct 26 08:32:06 ryzen7 kernel: [224041.662959] ? cpuidle_enter+0x17/0x20 Oct 26 08:32:06 ryzen7 kernel: [224041.662962] ? call_cpuidle+0x23/0x40 Oct 26 08:32:06 ryzen7 kernel: [224041.662964] ? do_idle+0x17f/0x1f0 Oct 26 08:32:06 ryzen7 kernel: [224041.662965] ? cpu_startup_entry+0x71/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.662968] ? rest_init+0x77/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.662971] ? start_kernel+0x482/0x4a3 Oct 26 08:32:06 ryzen7 kernel: [224041.662973] ? early_idt_handler_array+0x120/0x120 Oct 26 08:32:06 ryzen7 kernel: [224041.662975] ? x86_64_start_reservations+0x24/0x26 Oct 26 08:32:06 ryzen7 kernel: [224041.662977] ? x86_64_start_kernel+0x143/0x166 Oct 26 08:32:06 ryzen7 kernel: [224041.662979] ? start_cpu+0x14/0x14 Oct 26 08:32:06 ryzen7 kernel: [224041.662980] Task dump for CPU 1: Oct 26 08:32:06 ryzen7 kernel: [224041.662981] swapper/1 R running task 0 0 1 0x00000008 Oct 26 08:32:06 ryzen7 kernel: [224041.662983] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.662985] ? cpuidle_enter_state+0xfa/0x2d0 Oct 26 08:32:06 ryzen7 kernel: [224041.662986] ? cpuidle_enter+0x17/0x20 Oct 26 08:32:06 ryzen7 kernel: [224041.662988] ? call_cpuidle+0x23/0x40 Oct 26 08:32:06 ryzen7 kernel: [224041.662989] ? do_idle+0x17f/0x1f0 Oct 26 08:32:06 ryzen7 kernel: [224041.662991] ? cpu_startup_entry+0x71/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.662994] ? start_secondary+0x154/0x190 Oct 26 08:32:06 ryzen7 kernel: [224041.662995] ? start_cpu+0x14/0x14 Oct 26 08:32:06 ryzen7 kernel: [224041.662996] Task dump for CPU 6: Oct 26 08:32:06 ryzen7 kernel: [224041.662997] swapper/6 R running task 0 0 1 0x00000008 Oct 26 08:32:06 ryzen7 kernel: [224041.662998] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.663000] ? cpuidle_enter_state+0xfa/0x2d0 Oct 26 08:32:06 ryzen7 kernel: [224041.663002] ? cpuidle_enter+0x17/0x20 Oct 26 08:32:06 ryzen7 kernel: [224041.663003] ? call_cpuidle+0x23/0x40 Oct 26 08:32:06 ryzen7 kernel: [224041.663005] ? do_idle+0x17f/0x1f0 Oct 26 08:32:06 ryzen7 kernel: [224041.663006] ? cpu_startup_entry+0x71/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.663008] ? start_secondary+0x154/0x190 Oct 26 08:32:06 ryzen7 kernel: [224041.663009] ? start_cpu+0x14/0x14 Oct 26 08:32:06 ryzen7 kernel: [224041.663010] Task dump for CPU 7: Oct 26 08:32:06 ryzen7 kernel: [224041.663011] swapper/7 R running task 0 0 1 0x00000000 Oct 26 08:32:06 ryzen7 kernel: [224041.663012] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.663014] ? cpuidle_enter_state+0xfa/0x2d0 Oct 26 08:32:06 ryzen7 kernel: [224041.663016] ? cpuidle_enter+0x17/0x20 Oct 26 08:32:06 ryzen7 kernel: [224041.663017] ? call_cpuidle+0x23/0x40 Oct 26 08:32:06 ryzen7 kernel: [224041.663019] ? do_idle+0x17f/0x1f0 Oct 26 08:32:06 ryzen7 kernel: [224041.663020] ? cpu_startup_entry+0x71/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.663022] ? start_secondary+0x154/0x190 Oct 26 08:32:06 ryzen7 kernel: [224041.663023] ? start_cpu+0x14/0x14 Oct 26 08:32:06 ryzen7 kernel: [224041.663024] Task dump for CPU 12: Oct 26 08:32:06 ryzen7 kernel: [224041.663024] swapper/12 R running task 0 0 1 0x00000008 Oct 26 08:32:06 ryzen7 kernel: [224041.663026] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.663028] ? cpuidle_enter_state+0xfa/0x2d0 Oct 26 08:32:06 ryzen7 kernel: [224041.663029] ? cpuidle_enter+0x17/0x20 Oct 26 08:32:06 ryzen7 kernel: [224041.663031] ? call_cpuidle+0x23/0x40 Oct 26 08:32:06 ryzen7 kernel: [224041.663032] ? do_idle+0x17f/0x1f0 Oct 26 08:32:06 ryzen7 kernel: [224041.663034] ? cpu_startup_entry+0x71/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.663036] ? start_secondary+0x154/0x190 Oct 26 08:32:06 ryzen7 kernel: [224041.663037] ? start_cpu+0x14/0x14 Oct 26 08:32:06 ryzen7 kernel: [224041.663038] Task dump for CPU 13: Oct 26 08:32:06 ryzen7 kernel: [224041.663038] swapper/13 R running task 0 0 1 0x00000000 Oct 26 08:32:06 ryzen7 kernel: [224041.663039] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.663041] ? cpuidle_enter_state+0xfa/0x2d0 Oct 26 08:32:06 ryzen7 kernel: [224041.663043] ? cpuidle_enter+0x17/0x20 Oct 26 08:32:06 ryzen7 kernel: [224041.663044] ? call_cpuidle+0x23/0x40 Oct 26 08:32:06 ryzen7 kernel: [224041.663046] ? do_idle+0x17f/0x1f0 Oct 26 08:32:06 ryzen7 kernel: [224041.663047] ? cpu_startup_entry+0x71/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.663049] ? start_secondary+0x154/0x190 Oct 26 08:32:06 ryzen7 kernel: [224041.663050] ? start_cpu+0x14/0x14 Oct 26 08:32:06 ryzen7 kernel: [224041.663051] Task dump for CPU 15: Oct 26 08:32:06 ryzen7 kernel: [224041.663052] swapper/15 R running task 0 0 1 0x00000000 Oct 26 08:32:06 ryzen7 kernel: [224041.663053] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.663055] ? cpuidle_enter_state+0xfa/0x2d0 Oct 26 08:32:06 ryzen7 kernel: [224041.663056] ? cpuidle_enter+0x17/0x20 Oct 26 08:32:06 ryzen7 kernel: [224041.663058] ? call_cpuidle+0x23/0x40 Oct 26 08:32:06 ryzen7 kernel: [224041.663059] ? do_idle+0x17f/0x1f0 Oct 26 08:32:06 ryzen7 kernel: [224041.663061] ? cpu_startup_entry+0x71/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.663062] ? start_secondary+0x154/0x190 Oct 26 08:32:06 ryzen7 kernel: [224041.663063] ? start_cpu+0x14/0x14 Oct 26 08:32:06 ryzen7 kernel: [224041.663066] rcu_sched kthread starved for 15202 jiffies! g3043662 c3043661 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x1 Oct 26 08:32:06 ryzen7 kernel: [224041.663067] rcu_sched S 0 7 2 0x00000000 Oct 26 08:32:06 ryzen7 kernel: [224041.663068] Call Trace: Oct 26 08:32:06 ryzen7 kernel: [224041.663070] __schedule+0x232/0x700 Oct 26 08:32:06 ryzen7 kernel: [224041.663073] ? dequeue_task_fair+0x4ee/0xb20 Oct 26 08:32:06 ryzen7 kernel: [224041.663074] schedule+0x36/0x80 Oct 26 08:32:06 ryzen7 kernel: [224041.663076] schedule_timeout+0x1ea/0x3f0 Oct 26 08:32:06 ryzen7 kernel: [224041.663078] ? del_timer_sync+0x50/0x50 Oct 26 08:32:06 ryzen7 kernel: [224041.663080] rcu_gp_kthread+0x551/0x910 Oct 26 08:32:06 ryzen7 kernel: [224041.663083] kthread+0x109/0x140 Oct 26 08:32:06 ryzen7 kernel: [224041.663084] ? rcu_note_context_switch+0x100/0x100 Oct 26 08:32:06 ryzen7 kernel: [224041.663086] ? kthread_create_on_node+0x60/0x60 Oct 26 08:32:06 ryzen7 kernel: [224041.663088] ret_from_fork+0x2c/0x40 Oct 26 08:32:13 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:32:13 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:32:13 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:32:23 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:32:23 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:32:23 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:32:33 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:32:33 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:32:33 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:32:43 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:32:43 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:32:43 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:32:53 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:32:53 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:32:53 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:33:03 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:33:03 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:33:03 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:33:13 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:33:13 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:33:13 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:33:23 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:33:23 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:33:23 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:33:33 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:33:33 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:33:33 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:33:43 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:33:43 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:33:43 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:33:53 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:33:53 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:33:53 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:34:03 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:34:03 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:34:03 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:34:13 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:34:13 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:34:13 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:34:23 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:34:23 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:34:23 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:34:33 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:34:33 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:34:33 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:34:43 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:34:43 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:34:43 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:34:53 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:34:53 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 08:34:53 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 08:35:03 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 08:35:03 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 09:32:43 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. ... Oct 26 09:32:43 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 09:32:43 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 09:32:53 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 09:32:53 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 09:32:53 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 09:33:03 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 09:33:03 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 09:33:03 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. Oct 26 09:33:13 ryzen7 rtkit-daemon[3684]: The canary thread is apparently starving. Taking action. Oct 26 09:33:13 ryzen7 rtkit-daemon[3684]: Demoting known real-time threads. Oct 26 09:33:13 ryzen7 rtkit-daemon[3684]: Demoted 0 threads. <then garbage>
This issue appears to be known and is discussed at the following sites:
Uubuntu-16-04-compile-custom-kernel-for-ryzen
Ubuntu Launchpad bug 1690085
During the three day test, I did not observe any MCE erros or reboots. The issue I described though is of the same catagory and severe enough to discourage many linux users.
With such little known of the "Linux Performance Marginality Problem" causing segfaults while compiling, any crash or program failure I run into, I will always question if it's related to that problem or not. So to eliminate that potential, eliminate that problem.
RMA Timeline:
October 27th (Friday) - Initated RMA though AMD's website. Mentioned the segfault issue.
October 30th - AMD responded with instructions to send back the processor. No questions asked.
November 1st - Dropped packaged to FedEx.
November 3rd - FedEx site reports package will be delivered by the end of day Thursday November 9th.
November 8th - FedEx package delivered at 10:30 am local time.
November 9th - Comfirmation email from AMD that they received the package and validated the contents. Indicated to watch out for email notification when the replacement product is ready to ship. (It appears that this notification serves as the shipping notification.)
November 13th - Processor arrives.
November 15th - Tested processor for 1 hour running segfault test. Passed.
On to Windows 10 testing.
So far, I've encountered several windows 10 issues with my new build.
First off, I started with a clean install of Windows 10 Fall Creators Update I made with Microsoft's media creation tool. The install went fine, but after reboot and final setup, I wasn't able to install any applications. This appears to be a known issue and not Ryzen related - somehow during the install, permissions aren't handled properly for the administrator user. Creating a new administrator user can solve this problem. I went this route and began to experienced various BSODs. I decided to do another windows reinstall, but this time with the Spring Creators Update from the DVD I purchased. That install went fine too, but the BSODs persisted. I found a person who had a similar configuration and problem. He replaced the motherboard - taking out the Asus Prime X370 Pro and putting in an Asus Crosshair Hero VI. I picked one up, did the install, and now everything appears to be working BSOD free.