Thanks, ASX. I've already seen that thread.
My hardware support is fine.

NevilleGoddard wrote:Thanks, ASX. I've already seen that thread.
My hardware support is fine.

then ... have fun!

Will do.
When I get it running I'll post my story.

AMD confirm at least one Ryzen's bug:

http://phoronix.com/scan.php?page=news_ ... v-Response

Thanks for the article.
My Ryzen has had no problems so far and is performing extremely well.

However, I haven't been doing any compiling or "heavy" work with it yet. I haven't even overclocked it.

The problem is not in Windows and it also doesn't appear to affect the BSDs it only appears in Linux under certain conditions.

Systemd perhaps?

NevilleGoddard wrote: The problem is not in Windows and it also doesn't appear to affect the BSDs it only appears in Linux under certain conditions.

https://hothardware.com/news/freebsd-pr ... s-machines

Afaik, the problem has been reported on Linux primarily, but in DragonflyBSD too, FreeBSD as noted in the previous post, and also Windows when using WSL (Windows Subsystem Linux).

That said, it is not something easy to replicate, and probably one of the best way is to run the phoronix test suite, also mentioned in the link above.

I'm sure AMD will fix it soon.

I wish they'd provide Catalyst drivers for their GPUs in FreeBSD.

NevilleGoddard wrote:I'm sure AMD will fix it soon.

my understanding is that they already RMAed CPUs from affacted users, and issued a replacement CPU
a first round of RMA didn't fixed the issue;
a second round seems to have solved the problem, so it appear they are already to have a fix and actting upon customers requests.

I also understood they are working with hw manufacturer to provide a firmware fix, most likely you could see a UEFI update available at some point.