Date: Mon, 22 Jan 2018 13:07:30 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-stable@freebsd.org, Pete French <petefrench@ingresso.co.uk> Subject: Re: Ryzen issues on FreeBSD ? Message-ID: <tkrat.3c65225e2cd2f630@FreeBSD.org> In-Reply-To: <4e53080c-4257-d3b6-a097-0d54602e0e62@sentex.net> 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> <tkrat.4540dd6d35bd55a1@FreeBSD.org> <4e53080c-4257-d3b6-a097-0d54602e0e62@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22 Jan, Mike Tancsa wrote: > On 1/21/2018 3:24 PM, Don Lewis wrote: >>> >>> 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? > > > Are all the AMD accomodations that DragonFly did in FreeBSD ? > > http://lists.dragonflybsd.org/pipermail/commits/2017-August/626190.html We only lowered the top of user space by 4KB, which should be sufficient, and we unmapped the boundary page. The signal trampoline was already in a separate page than the stack.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.3c65225e2cd2f630>