Date: Sun, 3 Jun 2018 18:10:30 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Mike Tancsa <mike@sentex.net>, Don Lewis <truckman@FreeBSD.org> Cc: 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: <0e8b197f-15b2-b865-b532-cee2a20f2b42@ingresso.co.uk> In-Reply-To: <d32a66f4-2795-831e-6f4d-8d299ebfdbea@sentex.net> References: <tkrat.e96200e0b688ca3c@FreeBSD.org> <E1fP2HW-000HG4-KR@dilbert.ingresso.co.uk> <tkrat.5527722618de87c7@FreeBSD.org> <d32a66f4-2795-831e-6f4d-8d299ebfdbea@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> The compile bug has been fixed for me. However, last I checked I can > still freeze a system by generating a lot of network traffic between VMs > in either bhyve or virtbox. Its been a while since I tested (couple of > months) but I dont recall anything obviously committed that highlighted > that issue. Note this is on Epyc and Ryzen boxes Yes, it was your iperf3 tests which enable me to freeze the system with SMP enabled. With SMP disabled it works fine, however. have you tried that at all ? The only other settings I ahve are the global C-states and cool-n-quiet being disabled. I dont really care about either so havent tested re-enabling them. -pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0e8b197f-15b2-b865-b532-cee2a20f2b42>