From owner-freebsd-stable@freebsd.org  Wed Jan 17 23:38:45 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 C6C7FEBFA9D
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 17 Jan 2018 23:38:45 +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 9CE78687B6
 for <freebsd-stable@freebsd.org>; Wed, 17 Jan 2018 23:38:45 +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 w0HNd6sY074106
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL);
 Wed, 17 Jan 2018 23:39:08 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 w0HNAZJe027875
 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Wed, 17 Jan 2018 15:38:37 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Date: Wed, 17 Jan 2018 15:38:37 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Ryzen issues on FreeBSD ?
To: Nimrod Levy <nimrodl@gmail.com>
cc: Mike Tancsa <mike@sentex.net>, freebsd-stable@freebsd.org,
 Pete French <petefrench@ingresso.co.uk>
In-Reply-To: <CAMgUhpr+5HeBi1MRegs=XoKpdHW8-i+ec0k-DNaL_pcN6PCPKw@mail.gmail.com>
Message-ID: <tkrat.5ec856810e0c7ced@FreeBSD.org>
References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net>
 <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk>
 <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net>
 <tkrat.6d8f44d87e74fa14@FreeBSD.org>
 <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net>
 <CAMgUhpr+5HeBi1MRegs=XoKpdHW8-i+ec0k-DNaL_pcN6PCPKw@mail.gmail.com>
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: Wed, 17 Jan 2018 23:38:45 -0000

On 17 Jan, Nimrod Levy wrote:
> I'm running 11-STABLE from 12/9.  amdtemp works for me.  It also has the
> systl indicating that it it has the shared page fix. I'm pretty sure I've
> seen the lockups since then.  I'll update to the latest STABLE and see
> what  happens.
> 
> One weird thing about my experience is that if I keep something running
> continuously like the distributed.net client on 6 of 12 possible threads,
> it keeps the system up for MUCH longer than without.  This is a home server
> and very lightly loaded (one could argue insanely overpowered for the use
> case).

This sounds like the problem with the deep Cx states that has been
reported by numerous Linux users.  I think some motherboard brands are
more likely to have the problem.  See:
http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze