From owner-freebsd-stable@freebsd.org Fri Jan 19 22:32:38 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 66DBFECC7E6 for ; Fri, 19 Jan 2018 22:32:38 +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 3773B79A47 for ; Fri, 19 Jan 2018 22:32:38 +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 w0JMX0Su080947 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Jan 2018 22:33:01 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 w0JMTNqi028743 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 14:32:30 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 14:32:29 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French In-Reply-To: Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 22:32:38 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:32 PM, Peter Moody wrote: >> >> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about >> everything in all of these threads; disabling C state (no effect), >> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking >> voltage and cooling settings, rma'ing the board the cpu and the >> memory. nothing helped. >> >> last night I tried disabling SMT and, so far so good. > > > Is there anything that can be done to trigger the lockup more reliably ? > I havent found any patterns. I have had lockups with the system is 100% > idle and lockups when lightly loaded. I have yet to see any segfaults > or sig 11s while doing buildworld (make -j12 or make -j16 even) I never seen the idle lockup problem here. Prior to the shared page fix, I could almost always trigger a system hang or silent reboot by doing a parallel build of openjdk8.