Date: Fri, 27 Jul 2018 16:00:16 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Pete French <petefrench@ingresso.co.uk> Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, truckman@FreeBSD.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <20180727130016.GE2394@kib.kiev.ua> In-Reply-To: <548b493e-6a51-32ca-b3c1-216cac037e8b@ingresso.co.uk> References: <20180705133542.GG5562@kib.kiev.ua> <E1fb4mD-0006j7-SY@dilbert.ingresso.co.uk> <20180705145130.GH5562@kib.kiev.ua> <548b493e-6a51-32ca-b3c1-216cac037e8b@ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 27, 2018 at 12:01:09PM +0100, Pete French wrote: > So, I have been running the patched kernel for quiet a while now, and it > works fine for me, but last night I did hit a surprising issue - the > Linux emulator does not work on Ryzen / Epyc. I tried this on two > machines (both with the patches) and it coredumps when simply running > bash on both of them. I copied the OS over to an Intel machine, and that > works fine. > > I have not tried running with an unpatched kernel on the Ryzen machine > (I dont have one to hand) but I did try applying the sysctls to the > Intel box to see if that wuld cause the Linux binaries to crash. It didn't. I highly doubt that this can be related. BTW, I forgot about the patch. If nothing happens, I will commit it today.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180727130016.GE2394>