Date: Mon, 22 Oct 2018 12:30:17 +0300 From: Greg V <greg@unrelenting.technology> To: Hannes Hauswedell <h2+lists2018@fsfe.org> Cc: freebsd-current@freebsd.org Subject: Re: Current status of Ryzen (non-)support Message-ID: <1540200618.1834.0@smtp.migadu.com> 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 7:09 PM, Hannes Hauswedell=20 <h2+lists2018@fsfe.org> wrote: > Hi everyone, >=20 > I wanted to ask what the current status of Ryzen support is and/or > whether any new changes are planned. >=20 > 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 > * no full system freezes, but under load, e.g. building with 12=20 > threads, > programs start to segfault. > * memtest86 ran through without issues > * on a Linux dual boot I haven't had any issues >=20 > Is this a known problem? Anythings I can do about it? I thought the > Ryzen problem were only supposed to happen with first generation=20 > CPUs... First gen (R7 1700) here, overclocked to 3.9GHz, also running CURRENT=20 =97 never had any unexpected segfaults, even when building with 16=20 threads. The only bug is that the bottom (chipset) PCIe slot breaks when an NVMe=20 SSD is installed / chipset USB3 ports don't work: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231923 =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1540200618.1834.0>