Anybody planning a Ryzen build?

[L0rdRaiden]

14 minutes ago, limetech said:

 

 

In the massive bugzilla topic some people are now reporting a new "Power supply idle control" bios option:

https://bugzilla.kernel.org/show_bug.cgi?id=196683#c200

 

THanks for the answer.

But can you confirm looking at my logs that my freeze issue is related to this?, my "go" file was already edited to disable C6 state.

Now I have disable all Cstates in BIOS, I can't disbale just 1, if it doesn't work I will try the " Power supply idle control " which I'm suppose to use the option called "Typical current Idle", right?

[killeriq]

I have Asus x370 Prime Pro (Version 3803) with Ryzen 1700

 

I had (in BIOS) C6 States on AUTO and Unraid was stable - not sure if is enabled or how it really behaves.

So i set it to ENABLED and i get freeze sometime, need to hard reboot.

 

Is there any config in unRAID to disable/enable C States also? or this fix is only BIOS related? 

 

or option2:

Maybe its due to RAM (3200) OC to 3133 Mhz   All Ryzen chipsets/MB have issues with Ram clocks

 

Testing lower clocks now..

 

Thanks

Edited March 4, 2018 by killeriq

[L0rdRaiden]

36 minutes ago, killeriq said:

I have Asus x370 Prime Pro (Version 3803) with Ryzen 1700

 

I had (in BIOS) C6 States on AUTO and Unraid was stable - not sure if is enabled or how it really behaves.

So i set it to ENABLED and i get freeze sometime, need to hard reboot.

 

Is there any config in unRAID to disable/enable C States also? or this fix is only BIOS related? 

 

or option2:

Maybe its due to RAM (3200) OC to 3133 Mhz   All Ryzen chipsets/MB have issues with Ram clocks

 

Testing lower clocks now..

 

Thanks

Try this but in any case set c states in auto or disable, just in case

 

We ported a simplified version of the zenstates.py utility to C (to avoid including python in bzroot) which may be used to disable Ryzen C6 states (as workaround for Ryzen idle freeze issue). We have found that sometimes bios option to disable C6 does not exist or does not do the right thing. If you want to use this utility, we suggest that you edit the config/go file on your USB flash device. Add this line just before emhttp is invoked:

/usr/local/sbin/zenstates --c6-disable

 

 

But I would try first with the Typical current Idle setting in BIOS

[killeriq]

On 3/4/2018 at 10:12 PM, L0rdRaiden said:

Try this but in any case set c states in auto or disable, just in case

 

We ported a simplified version of the zenstates.py utility to C (to avoid including python in bzroot) which may be used to disable Ryzen C6 states (as workaround for Ryzen idle freeze issue). We have found that sometimes bios option to disable C6 does not exist or does not do the right thing. If you want to use this utility, we suggest that you edit the config/go file on your USB flash device. Add this line just before emhttp is invoked:

/usr/local/sbin/zenstates --c6-disable

 

 

But I would try first with the Typical current Idle setting in BIOS

 

Ok i set ram to 3000Mhz, set C6States on BIOs to auto...seems ok so far, will leave it few days what happens

 

btw this log Message is related to the "/usr/local/sbin/zenstates --c6-disable" u mention earlier?

 

Mar 5 23:32:00 unRAIDTower root: Fix Common Problems Version 2018.02.18
Mar 5 23:32:34 unRAIDTower root: Fix Common Problems: Other Warning: Mover logging is enabled
Mar 5 23:32:34 unRAIDTower root: Fix Common Problems: Warning: You have a Ryzen CPU, but Zenstates not installed.

[L0rdRaiden]

On 5/3/2018 at 11:40 PM, killeriq said:

 

Ok i set ram to 3000Mhz, set C6States on BIOs to auto...seems ok so far, will leave it few days what happens

 

btw this log Message is related to the "/usr/local/sbin/zenstates --c6-disable" u mention earlier?

 

Mar 5 23:32:00 unRAIDTower root: Fix Common Problems Version 2018.02.18
Mar 5 23:32:34 unRAIDTower root: Fix Common Problems: Other Warning: Mover logging is enabled
Mar 5 23:32:34 unRAIDTower root: Fix Common Problems: Warning: You have a Ryzen CPU, but Zenstates not installed.

The last message yes, the other 2 I don't think so.

BTW I would try this setting first if it works you won't need to disable c6 state

 

Typical current Idle setting in BIOS

[John_M]

On 04/03/2018 at 8:34 PM, killeriq said:

Maybe its due to RAM (3200) OC to 3133 Mhz   All Ryzen chipsets/MB have issues with Ram clocks

 

The maximum rated memory controller speed for 1000-series Ryzens is 2667* MHz and for the 2000-series APUs 2933* MHz. Anything higher than this is an overclock and is not guaranteed. It is not true to say that all Ryzen chipsets have issues with RAM clocks.

 

*Note: these are the effective speeds due to the DDR RAM. The actual speeds are 1333 and 1467 MHz, respectively.

[Pauven]

On 3/7/2018 at 11:13 AM, John_M said:

 

The maximum rated memory controller speed for 1000-series Ryzens is 2667* MHz and for the 2000-series APUs 2933* MHz. Anything higher than this is an overclock and is not guaranteed. It is not true to say that all Ryzen chipsets have issues with RAM clocks.

 

*Note: these are the effective speeds due to the DDR RAM. The actual speeds are 1333 and 1467 MHz, respectively.

 

Sorry, couldn't resist.  What John stated is 100% correct, though some details were omitted.

 

To build on John's statement, those maximum speeds are for Single-Rank DIMMs and typically only 2 populated slots.  The most likely configuration this would achieve is 16GB of installed RAM (2x 8GB Single-Rank). 

 

If you are running Dual-Rank DIMMs (think 16GB DIMMs, though I believe some 8GB DIMMs can also be Dual-Rank), or have installed memory into all 4 DIMM slots, then the maximum supported frequency drops.

 

And if you are running Dual-Rank DIMMs, AND have installed memory into all 4 DIMM slots, then the maximum supported frequency drops again.

 

On my Ryzen 7 1800x build, I have installed 64GB, so that means I am running both Dual-Rank DIMMs and I have populated all 4 memory slots.  While my memory is only running at DDR4-2400, technically that is overclocked, as maximum supported speed in this configuration is just DDR4-2133.

 

While my ASRock board runs my memory at DDR4-2400 without any special configuration, I am running overclocked according to AMD Ryzen specifications.

 

Depending upon the installed memory, Killer IQ may be overclocking the integrated Ryzen memory controller by nearly 50%.

 

While initially all Ryzen boards had issues with RAM clocks, the situation has greatly improved over the past year, so that Killer IQ's assertion is no longer valid.

 

As G.I. Joe says, "Knowing is half the battle."

 

Paul

Edited March 8, 2018 by Pauven
Typos

[jbartlett]

Just pulled the trigger on a Ryzen 1950X + Gigabyte X399 Designare EX. I'll post stats when it posts.

 

I don't know wither to cackle madly at upgrading from an 5930K or to pass a brick at the price.

[Jcloud]

12 hours ago, Pauven said:

As G.I. Joe says, "Knowing is half the battle."

The other half is red and blue lasers. 

 

It's not much, but I just made a public google sheet if people want to start dump their stats and give others an idea of what worked versus not.  There's a link to it in the hardware and CPU forums too.

 

https://tinyurl.com/unRAID-Ryzen-Survey

 

If you have no trust for the tinyurl:

https://docs.google.com/spreadsheets/d/1ozXM5qxRERahaxiHqYm2n1k0_9oTIkQj5-8qEhCQgGM/edit?usp=sharing

 

[Pauven]

10 hours ago, Jcloud said:

If you have no trust for the tinyurl:

 

It's like you're inside my head!

 

I added mine to the survey.  Did you want us to include our Username?

 

A couple notes on my build.  My Ryzen server has always been highly susceptible to the stability issues, and I always had to disable C-state Global Control in the BIOS to solve them.  For over a month now I've been running with "/usr/local/sbin/zenstates --c6-disable" in my go file, and C-state Global Control enabled, and I am running stable.

 

I don't do GPU passthrough, but I am currently running 4 VM's.  I'm running 3 VM's with Windows Server 2016 Standard, each with 4-cores and 16GB of RAM.  These are running an enterprise web application that I am developing against.  I'm also running a single VM with Windows Server 2016 Datacenter and SQL Server 2016, also with 4-cores and 16GB.  This VMs is the database server for the other 3 application servers.

 

Surprisingly, even with 16-cores and 64GB concurrently allocated, the unRAID server is running like a champ.  I'm averaging about 37% CPU load, and 57% memory usage.  The KVM technology is simply amazing.  And I can still stream Blu-ray movies.

 

I'm hammering these servers with requests, approximately 24 XML API requests per second per server, 40 HTTP requests per second per server, and 72 database queries per second, or 6.2 million DB queries per day.  My current unRAID uptime is 32 days (when I installed 6.4.1), and the VM uptime is approaching 18 days during this stress test session.

 

My only problem is that the database server ran out of disk storage as the audit table grew so large from all the DB requests...  hehehe.

 

Paul

Edited March 8, 2018 by Pauven

[CreZo]

Hey guys, I'm going to plan a switch from Intel (6700K) to AMD ( Ryzen 7 1700X). What should I pay attention to or keep in mind?

[jbartlett]

Depends on what you're doing with the 6700K.

[jammsen]

On 4.3.2018 at 9:34 PM, killeriq said:

I have Asus x370 Prime Pro (Version 3803) with Ryzen 1700

 

I had (in BIOS) C6 States on AUTO and Unraid was stable - not sure if is enabled or how it really behaves.

So i set it to ENABLED and i get freeze sometime, need to hard reboot.

 

Is there any config in unRAID to disable/enable C States also? or this fix is only BIOS related? 

 

or option2:

Maybe its due to RAM (3200) OC to 3133 Mhz   All Ryzen chipsets/MB have issues with Ram clocks

 

Testing lower clocks now..

 

Thanks

@killeriq

Would you be so kind to share your iommu groups with 2 gpus in slots?

Im got really weird iommu groups on the ASUS Prime B350 Plus with dual gpus, which i explained here: https://lime-technology.com/forums/topic/69986-problems-on-ryzen-5-with-asus-prime-b350-plus/ 

Basically they prevent me from using a dual gpu setup with unraid, which is what i want

Edited March 10, 2018 by jammsen
Updated text

[Donach]

1 hour ago, jammsen said:

@killeriq

Would you be so kind to share your iommu groups with 2 gpus in slots?

Im got really weird iommu groups on the ASUS Prime B350 Plus with dual gpus, which i explained here: https://lime-technology.com/forums/topic/69986-problems-on-ryzen-5-with-asus-prime-b350-plus/ 

Basically they prevent me from using a dual gpu setup with unraid, which is what i want

Did you use ACS Override?

If not, do.

 

If that is not enough, search my post back in the thread, where I explain how to setup the "multifunction" into unRaid startup. This helped me a lot to split the groups insanely (like really every device having its own group).

[jbartlett]

Motherboard: GIGABYTE X399 Designare EX

 

Installed a GeForce GTX 960 into PCIe slot #1 and a el-cheapo GeForce GT 610 into PCIe slot #4 and configured BIOS to use the 610 as the primary - though setting it to primary only worked with the 610 in slot 4.

 

IOMMU group 0:	[1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 1:	[1022:1453] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
IOMMU group 2:	[1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 3:	[1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 4:	[1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
IOMMU group 5:	[1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 6:	[1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
	[1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	[1022:145a] 09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a
	[1022:1456] 09:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
	[1022:145c] 09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
IOMMU group 7:	[1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
	[1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	[1022:1455] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455
	[1022:7901] 0a:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
	[1022:1457] 0a:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
IOMMU group 8:	[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
	[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
IOMMU group 9:	[1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
	[1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
	[1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
	[1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
	[1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
	[1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
	[1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric Device 18h Function 6
	[1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
IOMMU group 10:	[1022:1460] 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
	[1022:1461] 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
	[1022:1462] 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
	[1022:1463] 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
	[1022:1464] 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
	[1022:1465] 00:19.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
	[1022:1466] 00:19.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric Device 18h Function 6
	[1022:1467] 00:19.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
IOMMU group 11:	[1022:43ba] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset USB 3.1 xHCI Controller (rev 02)
	[1022:43b6] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller (rev 02)
	[1022:43b1] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset PCIe Bridge (rev 02)
	[1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	[1022:43b4] 02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	[1022:43b4] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	[1022:43b4] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	[1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02)
	[8086:1539] 04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
	[8086:24fd] 05:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
	[8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
IOMMU group 12:	[10de:104a] 08:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1)
	[10de:0e08] 08:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
IOMMU group 13:	[1022:1452] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 14:	[1022:1452] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 15:	[1022:1452] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 16:	[1022:1453] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
IOMMU group 17:	[1022:1452] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
IOMMU group 18:	[1022:1452] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
	[1022:1454] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	[1022:145a] 42:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a
	[1022:1456] 42:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
	[1022:145c] 42:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller
IOMMU group 19:	[1022:1452] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge
	[1022:1454] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
	[1022:1455] 43:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455
	[1022:7901] 43:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
IOMMU group 20:	[10de:1401] 41:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
	[10de:0fba] 41:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1)

USB Devices

Bus 001 Device 001:	ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002:	ID 8087:0a2b Intel Corp.
Bus 001 Device 003:	ID 048d:8295 Integrated Technology Express, Inc.
Bus 002 Device 001:	ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001:	ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002:	ID 154b:007a PNY Classic Attache Flash Drive
Bus 004 Device 001:	ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001:	ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002:	ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 006 Device 001:	ID 1d6b:0003 Linux Foundation 3.0 root hub

CPU Pairings

Pair 1:	cpu 0 / cpu 16
Pair 2:	cpu 1 / cpu 17
Pair 3:	cpu 2 / cpu 18
Pair 4:	cpu 3 / cpu 19
Pair 5:	cpu 4 / cpu 20
Pair 6:	cpu 5 / cpu 21
Pair 7:	cpu 6 / cpu 22
Pair 8:	cpu 7 / cpu 23
Pair 9:	cpu 8 / cpu 24
Pair 10: cpu 9 / cpu 25
Pair 11: cpu 10 / cpu 26
Pair 12: cpu 11 / cpu 27
Pair 13: cpu 12 / cpu 28
Pair 14: cpu 13 / cpu 29
Pair 15: cpu 14 / cpu 30
Pair 16: cpu 15 / cpu 31

 

[jammsen]

Well the guys from ASUS just did forget to implement that feature in the BIO S i guess, even the Beta one: 

https://www.asus.com/de/Motherboards/PRIME-B350-PLUS/HelpDesk_BIOS/

 

@donach

Yes i used ACS override, the settings are posted in my thread.

Edited March 10, 2018 by jammsen

[Jcloud]

On 3/8/2018 at 10:38 AM, Pauven said:

Did you want us to include our Username?

 

Optional? It would be nice for asking questions, and follow up by other members, but I could see sparks flying off the tin-foil hat for some.  Just added a header to the sheet.

 

[killeriq]

On 3/7/2018 at 3:22 PM, L0rdRaiden said:

The last message yes, the other 2 I don't think so.

BTW I would try this setting first if it works you won't need to disable c6 state

 

Typical current Idle setting in BIOS

Ive set RAM back to 3066 Mhz from 3133 and issues with freezing are gone.

 

Seems like if i want to run RAM on 3200Mhz i need to get Asus Crosshair Hero 6 MB , to replace mine Asus X370 Prime Pro...As i have confirmed with few users running Hero6 that all is fine on 3200Mhz.

 

This message you mention - i have Cstates ENABLED in BIOS, so if i use "/usr/local/sbin/zenstates --c6-disable" it will have same effect as if i disable them in BIOS?

Mar 10 04:40:44 unRAIDTower root: Fix Common Problems: Warning: You have a Ryzen CPU, but Zenstates not installed.

 

 

@jammsen - currently i have only 1x AMD card in the Server, but within a week i will put 2x 1080ti then i can share details...

[jammsen]

16 hours ago, killeriq said:

Ive set RAM back to 3066 Mhz from 3133 and issues with freezing are gone.

 

Seems like if i want to run RAM on 3200Mhz i need to get Asus Crosshair Hero 6 MB , to replace mine Asus X370 Prime Pro...As i have confirmed with few users running Hero6 that all is fine on 3200Mhz.

 

This message you mention - i have Cstates ENABLED in BIOS, so if i use "/usr/local/sbin/zenstates --c6-disable" it will have same effect as if i disable them in BIOS?

Mar 10 04:40:44 unRAIDTower root: Fix Common Problems: Warning: You have a Ryzen CPU, but Zenstates not installed.

 

 

@jammsen - currently i have only 1x AMD card in the Server, but within a week i will put 2x 1080ti then i can share details...

Hey @killeriq  and @Donachi updated my post, i changed the mainboard, which was a REALLY huge difference, i think its because of the different architecture between the B350 and X370 chipset, that the iommu groups are really really weird on b350 ... or its just lazyness on the vendorsite i guess?

 

Anyway, it works good right now, please take a look at my post for more details and of course, thanks for the help!

Edited March 11, 2018 by jammsen

[jbartlett]

I'm getting a ton of the following errors on my  GIGABYTE X399 Designare EX whenever I write to the array or cache drives though no data corruption seems to be evident. Based on my research, enabling a kernel PCI option can change how the PCIe bus is accessed and resolve/suppress these errors. So my question is - how do I toggle kernel options?

 

Mar 11 03:25:41 NASDev kernel: pcieport 0000:00:01.1:    [ 6] Bad TLP
Mar 11 03:26:31 NASDev kernel: pcieport 0000:00:01.1: AER: Corrected error received: id=0000
Mar 11 03:26:31 NASDev kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0009(Receiver ID)
Mar 11 03:26:31 NASDev kernel: pcieport 0000:00:01.1:   device [1022:1453] error status/mask=00000040/00006000
Mar 11 03:26:31 NASDev kernel: pcieport 0000:00:01.1:    [ 6] Bad TLP
Mar 11 03:26:51 NASDev kernel: pcieport 0000:00:01.1: AER: Corrected error received: id=0000
Mar 11 03:26:51 NASDev kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0009(Receiver ID)
Mar 11 03:26:51 NASDev kernel: pcieport 0000:00:01.1:   device [1022:1453] error status/mask=00000080/00006000
Mar 11 03:26:51 NASDev kernel: pcieport 0000:00:01.1:    [ 7] Bad DLLP
Mar 11 03:27:18 NASDev kernel: pcieport 0000:00:01.1: AER: Corrected error received: id=0000
Mar 11 03:27:18 NASDev kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0009(Receiver ID)
Mar 11 03:27:18 NASDev kernel: pcieport 0000:00:01.1:   device [1022:1453] error status/mask=00000080/00006000
Mar 11 03:27:18 NASDev kernel: pcieport 0000:00:01.1:    [ 7] Bad DLLP
Mar 11 03:28:38 NASDev kernel: pcieport 0000:00:01.1: AER: Multiple Corrected error received: id=0000
Mar 11 03:28:38 NASDev kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0009(Receiver ID)
Mar 11 03:28:38 NASDev kernel: pcieport 0000:00:01.1:   device [1022:1453] error status/mask=00000040/00006000

 

nasdev-diagnostics-20180311-0149.zip

Edited March 11, 2018 by jbartlett

[jbartlett]

7 hours ago, jbartlett said:

I'm getting a ton of the following errors on my  GIGABYTE X399 Designare EX whenever I write to the array or cache drives though no data corruption seems to be evident. Based on my research, enabling a kernel PCI option can change how the PCIe bus is accessed and resolve/suppress these errors. So my question is - how do I toggle kernel options?

 

Edit the syslinux.cfg file.

append initrd=/bzroot pci=nommconf

Edited March 12, 2018 by jbartlett

[Jcloud]

Saw this cnet article, four new chip-level security flaws found in Ryzen and EPYC. There might be a few more bumps in the road still ahead.

[John_M]

4 hours ago, Jcloud said:

Saw this cnet article, four new chip-level security flaws found in Ryzen and EPYC. There might be a few more bumps in the road still ahead.

 

There's something not right about that article. I don't believe it to be true. If it were the news would have been handled very differently. Someone is out to cause mischief. At best CTS-Labs has acted irresponsibly by disclosing after only 24 hours, at worst there's real malice involved. Expect retractions and recriminations.

[Jcloud]

26 minutes ago, John_M said:

There's something not right about that article. I don't believe it to be true. If it were the news would have been handled very differently. Someone is out to cause mischief. At best CTS-Labs has acted irresponsibly by disclosing after only 24 hours, at worst there's real malice involved. Expect retractions and recriminations.

Admitting, shortly after I did see a second article about AMD claiming fowl-play, and thought people were trying to manipulate their stock price. Got busy at work and forgot to make mention of that. Hopefully it's a false alarm, and if so, sorry for hitting the klaxon. Must also admit CNET isn't the best of sites last five years or so, probably should have taken it with a grain of salt myself.

[tjb_altf4]

"The researchers gave AMD less than 24 hours to look at the vulnerabilities and respond before publishing the report. Standard vulnerability disclosure calls for at least 90 days notice so companies have time to address flaws properly. Disclosing a vulnerability to the public without first giving a company enough time to fix it can be irresponsible, as it leaves the flaw open for attackers to exploit. Google's researchers gave Intel six months to fix issues related to Spectre and Meltdown."

 

There may be merit to the finds, but they've lost some credibility there.