Date: Tue, 26 Jun 2018 14:29:19 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Pete French <petefrench@ingresso.co.uk> Cc: eric@vangyzen.net, mike@sentex.net, truckman@FreeBSD.org, avg@freebsd.org, freebsd-stable@freebsd.org, freebsd@hda3.com Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <20180626112919.GK2430@kib.kiev.ua> In-Reply-To: <E1fXlFu-0000rF-3y@dilbert.ingresso.co.uk> References: <9233bded-3ea2-dc46-19bf-f9a7eef7fa6b@vangyzen.net> <E1fXlFu-0000rF-3y@dilbert.ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 26, 2018 at 11:31:26AM +0100, Pete French wrote: > > On 06/18/2018 09:34, Pete French wrote: > > > Preseumably in the slightly longer term these workarounds go into the > > > actual kernel if it detects Ryzen ? > > > > Yes, Kostik said he would code this into the kernel after he gets enough > > feedback. > > So, I've been running with the sysctl and cputl fixes from > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > for a couple of weeks now, with all the default settings back on (including > SMT) and it now completely stable, so consider this one more point of feedback If you run without the script, with the same settings, do you experience problems ? Also, please show the 100 first lines of the verbose boot dmesg on this machine.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180626112919.GK2430>