From owner-freebsd-stable@freebsd.org Thu Jan 25 13:49:11 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 39739ED8B76 for ; Thu, 25 Jan 2018 13:49:11 +0000 (UTC) (envelope-from nbe@renzel.net) Received: from nijmegen.renzel.net (mx1.renzel.net [195.243.213.130]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.renzel.net", Issuer "renzel.net Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BC7C17D17F for ; Thu, 25 Jan 2018 13:49:10 +0000 (UTC) (envelope-from nbe@renzel.net) X-Virus-Scanned: GDATA Antivirus at gdata-milter.renzel.de.isb X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=-8.0 required=7.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 Received: from dublin.vkf.isb.de.renzel.net (unknown [10.0.0.80]) by nijmegen.renzel.net (smtpd) with ESMTP id BCD1B1414876 for ; Thu, 25 Jan 2018 14:48:30 +0100 (CET) Received: from asbach.renzel.net (unknown [172.18.96.1]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTPA id B6B03867B3 for ; Thu, 25 Jan 2018 14:48:30 +0100 (CET) Subject: Re: Ryzen issues on FreeBSD ? References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> To: freebsd-stable@freebsd.org From: Nils Beyer Message-ID: <8c8e458b-8ddd-08e6-1d2e-487d95583790@renzel.net> Date: Thu, 25 Jan 2018 14:48:30 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.net 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: Thu, 25 Jan 2018 13:49:11 -0000 On 01/17/18 14:38, Mike Tancsa wrote: > However, we are seeing random lockups on both boxes. [...] go into your BIOS: - load default settings - disable SMT - disable Cool&Quiet - disable global C-state control - disable anything with C-states only with SMT _and_ Cool&Quiet _and_ C-state-stuff all together disabled, my system is still running (uptime now is 49 days). Every other fiddling around with RAM, PSU and timing settings is fruitless. Before, my system locked up after a run time of six to ten days. And, yes, I have a replacement CPU and the shared page fix active - these didn't help. This does not help with your compilation problems though... BR, Nils