Date: Wed, 24 Jan 2018 17:29:19 +0100 From: Alban Hertroys <haramrae@gmail.com> To: Mike Tancsa <mike@sentex.net> Cc: Mark Millard <marklmi26-fbsd@yahoo.com>, nimrodl@gmail.com, michaelp@bsquare.com, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) Message-ID: <CAF-3MvMzoC-j1tcvY9PiB9g3pBYOwDwe0frRs_mARjmZryjKrw@mail.gmail.com> In-Reply-To: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> References: <A6A50EB1-6944-40B4-9F33-002336F582E6@yahoo.com> <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 January 2018 at 15:42, Mike Tancsa <mike@sentex.net> wrote: > b) CPUs manufactured prior to week 25 (some say week 33?) have a > hardware defect that manifests itself as segfaults in heavy compiles. I > was able to confirm this on 1 of the CPUs I had using a Linux setup. It > seems to confirm this, you need to physically look at the CPU for the > manufacturing date :( Not sure how to trigger it on FreeBSD reliably, > but there is a github project I used to verify on Linux > (https://github.com/suaefar/ryzen-test) According to post #39 in the referenced Linux thread (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085): "It was officially fixed for all ryzen manufactured after week 30." I currently have a Ryzen 1600X from week 17/30, which suggests it will have the bug. Unfortunately, I don't have it built into a system yet as I'm waiting for DDR4 prices to become reasonable again before ordering any, so I can't test it. I'm not sure how solid this info is, should I RMA it without even having tested that it has a problem? Alban Hertroys -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF-3MvMzoC-j1tcvY9PiB9g3pBYOwDwe0frRs_mARjmZryjKrw>