From owner-freebsd-stable@freebsd.org  Sun Jan 21 20:24:16 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
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 23458EB8EB4
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 21 Jan 2018 20:24:16 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "amnesiac", Issuer "amnesiac" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 023427AC61
 for <freebsd-stable@freebsd.org>; Sun, 21 Jan 2018 20:24:15 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org ([76.212.85.177])
 by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w0LKOYg7088898
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL);
 Sun, 21 Jan 2018 20:24:35 GMT (envelope-from truckman@FreeBSD.org)
Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w0LKHnFE040195
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Sun, 21 Jan 2018 12:24:02 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Date: Sun, 21 Jan 2018 12:24:02 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Ryzen issues on FreeBSD ?
To: Willem Jan Withagen <wjw@digiware.nl>
cc: Pete French <petefrench@ingresso.co.uk>, freebsd-stable@freebsd.org
In-Reply-To: <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl>
Message-ID: <tkrat.4540dd6d35bd55a1@FreeBSD.org>
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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-Disposition: INLINE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jan 2018 20:24:16 -0000

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?