From owner-freebsd-stable@freebsd.org Sun Apr 22 21:29:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F876F9148B for ; Sun, 22 Apr 2018 21:29:59 +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 CD1307BD8D; Sun, 22 Apr 2018 21:29:58 +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 w3MLVEcq035582 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sun, 22 Apr 2018 21:31:16 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 w3MLThaJ082655 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 22 Apr 2018 14:29:44 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Sun, 22 Apr 2018 14:29:38 -0700 (PDT) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French cc: eric@vangyzen.net, freebsd@hda3.com, avg@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: Message-ID: References: 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: Sun, 22 Apr 2018 21:29:59 -0000 On 20 Apr, Pete French wrote: > So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work....). All went smoothl;y, checked it > booted up, used it for 15 minutes, was impressed by the speed and went home. > > ...and by the time I got home, an hour or so later, it had locked up hard. > > I was somewhat dissapointed, as I had seen various fixes go in,. and had hoped > the issues were fixed. This morning I have booted the machine back up, > tweaking the BIOPS to do things mentioned in this thread, viz: > > Disable Turbo Boost > Disable SMT > Disable global C-states > > The memory was already ruunning correctly at 2133 (though I have locked that > in the BIOS too) and I was already using kern.eventtimer.periodic=1, so > the lockup was not related to those. Its the latest BIOS, and a -STABLE > build from yesterday. > > I suspect it will now be stable, but I was wondering if anyone was any further > forward on working out which of the settings above are the ones which 'fix' > the issue - or indeed if its really fixed, by them or just made far less likely > to happen. > > Anyone got any more comments on this ? In terms of hangs and system crashes, my Ryzen system has been stable since the fix to relocate the shared page. The random segfault problem during parallel builds went away when I RMAed my original, early-build CPU. This commit: r329254 | kib | 2018-02-13 16:31:45 -0800 (Tue, 13 Feb 2018) | 43 lines Ensure memory consistency on COW. Fixed most of the remaining random port build errors that I had. I think the only remaining problem is random build failures of guile-related ports, but I also see these on my FX-8320E, so they are not Ryzen-specific. Pretty much all of my BIOS settings are the defaults. I suspect that the idle hang issues are motherboard and/or BIOS specific. For the record my motherboard is a Gigabyte GA-AX370-Gaming 5.