Date: Wed, 24 Jan 2018 09:35:01 -0800 From: Peter Moody <freebsd@hda3.com> To: Alban Hertroys <haramrae@gmail.com> Cc: Mike Tancsa <mike@sentex.net>, Mark Millard <marklmi26-fbsd@yahoo.com>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Nimrod Levy <nimrodl@gmail.com> Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) Message-ID: <CADbMJxmnv3dnU-0XuCpVrbF2m8WH-tVk=YECnyZi7JYag00zgg@mail.gmail.com> In-Reply-To: <CAF-3MvMzoC-j1tcvY9PiB9g3pBYOwDwe0frRs_mARjmZryjKrw@mail.gmail.com> References: <A6A50EB1-6944-40B4-9F33-002336F582E6@yahoo.com> <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> <CAF-3MvMzoC-j1tcvY9PiB9g3pBYOwDwe0frRs_mARjmZryjKrw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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've seen the blanking screen lockup on a 1600X from 1739SUS and 1740SUS. Only with SMT enabled though. On the 1739 chip I'm also seeing cc segfaults on make -j 18 buildworld (again, just with SMT enabled). This is all so frustrating. > 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. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADbMJxmnv3dnU-0XuCpVrbF2m8WH-tVk=YECnyZi7JYag00zgg>