Date: Tue, 24 Apr 2018 15:39:17 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Mike Tancsa <mike@sentex.net>, 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: <1b210d7d-dcbb-d8d5-ecf9-c2277c90dd9b@ingresso.co.uk> In-Reply-To: <e41b6aa4-7ac1-44b4-8b88-fd744e31f7e2@sentex.net> References: <E1fAaRY-0000nB-Ut@dilbert.ingresso.co.uk> <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> <e41b6aa4-7ac1-44b4-8b88-fd744e31f7e2@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
yes, I too think its definitely a Ryzen isssue with FreeBSD - is there a way you could try it (at least on the Desktop) with SMT off ? I havbe the following options tunred off: SMT Glocal C states Cool-n-quiet Core boost The last few obviously tweak processor clocks and thus dont surprise me too much as a soource of instabuloty, but I am surprised that SMT causes issues, as that should (I belive) simply present as two cores. On 24/04/2018 15:22, Mike Tancsa wrote: > 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 > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1b210d7d-dcbb-d8d5-ecf9-c2277c90dd9b>