From owner-freebsd-stable@freebsd.org Mon Nov 26 16:25:30 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 03608113B8DE for ; Mon, 26 Nov 2018 16:25:30 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 8BC4C7B5D9 for ; Mon, 26 Nov 2018 16:25:28 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [82.47.240.30] (helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gRJhM-000Ebu-0N for freebsd-stable@freebsd.org; Mon, 26 Nov 2018 16:25:24 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: 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> From: Pete French Message-ID: <0778a0b2-51b6-5c08-b777-cbeff7cae54f@ingresso.co.uk> Date: Mon, 26 Nov 2018 16:25:29 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:64.0) Gecko/20100101 Thunderbird/64.0 MIME-Version: 1.0 In-Reply-To: <50ae7040-b0c4-4092-c5d0-75ed86ed4845@ingresso.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 8BC4C7B5D9 X-Spamd-Result: default: False [4.44 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:b90:3002:411::3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; RDNS_NONE(1.00)[]; NEURAL_SPAM_MEDIUM(0.27)[0.266,0]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(0.73)[0.730,0]; MX_GOOD(-0.01)[ingresso-co-uk.mail.protection.outlook.com,ingresso-co-uk.mail.protection.outlook.com]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_ALLOW(-0.50)[ingresso.co.uk,none]; NEURAL_SPAM_LONG(0.77)[0.774,0]; RECEIVED_SPAMHAUS_PBL(0.00)[30.240.47.82.zen.spamhaus.org : 127.0.0.11]; R_DKIM_NA(0.00)[]; IP_SCORE(-0.02)[country: GB(-0.10)]; ASN(0.00)[asn:16082, ipnet:2a02:b90::/32, country:GB]; HFILTER_HOSTNAME_UNKNOWN(2.50)[]; SUBJECT_HAS_QUESTION(0.00)[]; FROM_EQ_ENVFROM(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:25:30 -0000 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? cheers, -pete. PS: I went to 12 to get Linux emulation back, as this is still broken on Ryzen under 11 I believe.