From owner-freebsd-stable@freebsd.org Wed Jan 17 20:39:45 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 908C7EB5FE4 for ; Wed, 17 Jan 2018 20:39: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 70DA981060 for ; Wed, 17 Jan 2018 20:39: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 w0HKe5ca073755 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 17 Jan 2018 20:40:07 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 w0HKdZbV022581 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jan 2018 12:39:36 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Wed, 17 Jan 2018 12:39:30 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Pete French , freebsd-stable@freebsd.org In-Reply-To: <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> 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> 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: Wed, 17 Jan 2018 20:39:45 -0000 On 17 Jan, Mike Tancsa wrote: > On 1/17/2018 8:43 AM, Pete French wrote: >> >> Are you running the latest STABLE ? There were some patches for Ryzen >> which went in I belive, and might affect te stability. Specificly the >> chnages to stop it locking up when executing code in the top page ? > > Hi, > I was testing with RELENG_11 as of 2 days ago. The fix seems to be there > > # sysctl -A hw.lower_amd64_sharedpage > hw.lower_amd64_sharedpage: 1 > > Would love to find a class of motherboard that pushes its "You dont need > to dork around with any BIOS settings. It just works. Oh, and we have a > hardware watchdog too".... ipmi would be stellar. The shared page change fixed the random lockup and silent reboot problem for me. I've got a 1700X eight core CPU and a Gigabyte X370 Gaming 5. I did have to RMA my CPU (it was an early one) because it had the problem with random segfaults that seemed to be triggered by process migration between CPU cores. I still haven't switched over to using it for package builds because I see more random fallout than on my older package builder. I'm not blaming the hardware for that at this point because I see a lot of the same issues on my older machine, but less frequently. One thing to watch (though it should be less critical with a six core CPU) is VRM cooling. I removed the stupid plastic shroud over the VRM sink on my motherboard so that it gets some more airflow.