Date: Sun, 21 Oct 2018 20:33:27 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Hannes Hauswedell <h2+lists2018@fsfe.org> Cc: freebsd-current@freebsd.org Subject: Re: Current status of Ryzen (non-)support Message-ID: <20181021173327.GJ5335@kib.kiev.ua> In-Reply-To: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org> References: <632587eb-2c27-2e7f-2571-25c06025cd80@fsfe.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 21, 2018 at 06:09:50PM +0200, Hannes Hauswedell wrote: > Hi everyone, > > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. > > My situation: > * second generation Ryzen: 2600X > * running -CURRENT > * I have done the things described here: > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html This was based on the public errata document for the first gen ryzen. I am not aware of the erratas ('revision guides' in AMD terminology) for the second gen ryzens. For now you can only get fixes for microcode from your BIOS updates. > * no full system freezes, but under load, e.g. building with 12 threads, > programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues Or look at the Linux sources and see if any workarounds are applied and chicken bits are set for your CPU. > > Is this a known problem? Anythings I can do about it? I thought the > Ryzen problem were only supposed to happen with first generation CPUs... > > Thanks and regards, > Hannes >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181021173327.GJ5335>