Date: Wed, 25 Apr 2018 10:14:04 +0100 From: Pete French <petefrench@ingresso.co.uk> To: Don Lewis <truckman@FreeBSD.org>, Mike Tancsa <mike@sentex.net> Cc: nimrodl@gmail.com, 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: <3533f777-e708-623d-b280-5be418fd4d50@ingresso.co.uk> In-Reply-To: <tkrat.5235cb463511b830@FreeBSD.org> 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> <tkrat.5235cb463511b830@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> It would be interesting to test other AMD CPUs. I think AMD and Intel > have some differences in the virtualization implementations. I've been using AMD CPU's pretty extensively since the early 90's - back then I was running NeXTStep and out of the three Intel alternatives it was the only one which ran properly. Never seen anything like this before now though. In particular this Ryzen replaces the CPU on an old Phenom II - i.e. its the same disc and hence the same OS and VirtualBox config - and that ran fine. So theres something odd about the Ryzen here. Am also not sure its to do with the virtualisation - I got my first lockup with no virtualisation going on at all. Disablign SMT and the system hasnt locked, despite heavy virtualbox use. -pete.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3533f777-e708-623d-b280-5be418fd4d50>