Date: Sun, 21 Jan 2018 12:24:02 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: Willem Jan Withagen <wjw@digiware.nl> Cc: Pete French <petefrench@ingresso.co.uk>, freebsd-stable@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? Message-ID: <tkrat.4540dd6d35bd55a1@FreeBSD.org> In-Reply-To: <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <e2d004c63e414022ce48b5b50959c302@foolishgames.com> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> <tkrat.943da3fc20539e05@FreeBSD.org> <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Jan, Willem Jan Withagen wrote: > On 19/01/2018 23:29, Don Lewis wrote: >> On 19 Jan, Pete French wrote: >>> Out of interest, is there anyone out there running Ryzen who *hasnt* >>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine >>> works fine" >> >> No hangs or silent reboots here with either my original CPU or warranty >> replacement once the shared page fix was in place. > > Perhaps a too weird reference: > > I have supplied a customer with a Ryzen5 and a 350MB motherboard. > But he runs Windows 10, but I haven't heard him complain about anything > like this. > But I'll ask him specific. Only the BSDs were affected by the shared page issue. I think Linux already had a guard page. I don't think Windows was affected by the idle C-state issue. I suspect it is caused by software not doing the right thing during C-state transitions, but the publicly available documentation from AMD is pretty lacking. The random segfault issue is primarily triggered by heavy parallel software build loads and how many Windows users do that?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.4540dd6d35bd55a1>