Date: Mon, 23 Apr 2018 10:40:37 +0100 From: Pete French <petefrench@ingresso.co.uk> To: petefrench@ingresso.co.uk, nimrodl@gmail.com Cc: truckman@freebsd.org, freebsd@hda3.com, freebsd-stable@freebsd.org, eric@vangyzen.net, avg@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <E1fAXxd-000JYr-Sh@dilbert.ingresso.co.uk> In-Reply-To: <CAMgUhppOgnS2ZmeN%2B0ruj-AsDWLNvU_64EteynjS2oq_jDTzog@mail.gmail.com> References: <a9eef511-6478-b373-590e-086029b4f97b@vangyzen.net> <E1f9U0O-0002Bl-O7@dilbert.ingresso.co.uk> <CAMgUhpqaVBnD=uKwoTCB5OBGDofU3CQRdDWy=v4OJ_Ydbaqe1w@mail.gmail.com> <CAMgUhppOgnS2ZmeN%2B0ruj-AsDWLNvU_64EteynjS2oq_jDTzog@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> And of course now that we say something about it, I get a lockup > overnight... Sods law I guess. Mine survived the weekend quite happily though, so am fairly pleased with that. Am going to try the test case that Mike Tancsa posted to see if I can get it to lockup today though,. now that I am in front of it to reset of required. Will report results either way... -pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1fAXxd-000JYr-Sh>