From owner-freebsd-stable@freebsd.org Mon Nov 26 16:29:00 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 8F554113B9DB for ; Mon, 26 Nov 2018 16:29:00 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 197177B74E for ; Mon, 26 Nov 2018 16:29:00 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from disco.vangyzen.net (unknown [70.97.188.230]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 87C45564B6; Mon, 26 Nov 2018 10:28:51 -0600 (CST) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French , freebsd-stable@freebsd.org References: <20180705133542.GG5562@kib.kiev.ua> <20180705145130.GH5562@kib.kiev.ua> <548b493e-6a51-32ca-b3c1-216cac037e8b@ingresso.co.uk> <20180727130016.GE2394@kib.kiev.ua> <76f693ec-d6f5-4261-ac25-13100f4b2f5f@ingresso.co.uk> <50ae7040-b0c4-4092-c5d0-75ed86ed4845@ingresso.co.uk> <0778a0b2-51b6-5c08-b777-cbeff7cae54f@ingresso.co.uk> From: Eric van Gyzen Message-ID: Date: Mon, 26 Nov 2018 10:28:50 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <0778a0b2-51b6-5c08-b777-cbeff7cae54f@ingresso.co.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 197177B74E X-Spamd-Result: default: False [-3.91 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[vangyzen.net]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: hotblack.vangyzen.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.80)[-0.800,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; IP_SCORE(-0.80)[asn: 36236(-3.92), country: US(-0.09)]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:36236, ipnet:2607:fc50:1000::/36, country:US]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2018 16:29:00 -0000 On 11/26/18 10:25 AM, Pete French wrote: > Foolwing up an old thread I know, but my ssystem ahs been pretty stable > until recently, when it started locking up about one a week at least. > This co-incided with me doing two things to it: > > 1) Doubling the amount of RAM in it to 16 gig, using RAM which runs a > bit faster than the original sticks (2667 instead of 2400) > > 2) Upgrading to FreeBSD 12 BET4 > > Now, I am really hoping the lockups are down to the RAM and that I just > need to underclock it a bit, but I am a bit worried by the fact it > happened the ame time as I went to 12. Has anyone else seen any issues > under 12 when stable under 11? My Ryzen has never run 11, but I have never seen a single problem on 12. As you suggest, it's probably due to the particular hardware combination. If updating the BIOS doesn't help, I agree that lowering the memory clock is the best next step. Eric