Date: Tue, 24 Apr 2018 10:22:46 -0400 From: Mike Tancsa <mike@sentex.net> To: Pete French <petefrench@ingresso.co.uk>, nimrodl@gmail.com Cc: truckman@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <e41b6aa4-7ac1-44b4-8b88-fd744e31f7e2@sentex.net> In-Reply-To: <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> References: <E1fAaRY-0000nB-Ut@dilbert.ingresso.co.uk> <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/24/2018 10:01 AM, Pete French wrote: > > Well, I ranh the iperf tests between real machine for 24 hours and that > worked fine. I also then spun up a Virtualbox with Win10 in it, and ran > iuperf to there at the same time as doing it betwene real machines, and > also did a full virus scan to exercise the disc. the idea being to > replicate Mondays lockup. I was able to lock it up with vbox. bhyve was just a little easier to script and also I figured would be good to get VBox out of the mix in case it was something specific to VBox. I dont recall if I tried it with SMT disabled. Regardless, on Intel based systems I ran these tests for 72hrs straight without issue. I can sort of believe hardware issue or flaky motherboard BIOSes (2 ASUS MBs, 1 MSI MB, 3 Ryzen chips), but the fact that two server class MBs from SuperMicro along with an Epyc chip also does the same thing makes me think something specific to FreeBSD and this class of AMD CPU :( ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e41b6aa4-7ac1-44b4-8b88-fd744e31f7e2>