From owner-freebsd-stable@freebsd.org Sun Jan 21 20:50:53 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11D0FEBA5FA for ; Sun, 21 Jan 2018 20:50:53 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA7567BB70; Sun, 21 Jan 2018 20:50:52 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 043752E952; Sun, 21 Jan 2018 21:50:50 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68mqbj8tkfxL; Sun, 21 Jan 2018 21:50:49 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 643652E951; Sun, 21 Jan 2018 21:50:49 +0100 (CET) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Pete French , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> From: Willem Jan Withagen Message-ID: <86eba4e4-f9a7-7177-a6bf-12700b1defa0@digiware.nl> Date: Sun, 21 Jan 2018 21:50:50 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: nl Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2018 20:50:53 -0000 On 21/01/2018 21:24, Don Lewis wrote: > 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? This is an adobe workstation where several users remote login and do work. So I would assume that the system is seriously (ab)used. Adn as expected I'm know aware of any of the detailed things that Windows does while powering into lesser active states. --WjW