From owner-freebsd-stable@freebsd.org Mon Nov 26 17:17:56 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 47C3E113D0FB for ; Mon, 26 Nov 2018 17:17:56 +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 AC1637DBC8; Mon, 26 Nov 2018 17:17:55 +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 1gRKWA-000FJU-Df; Mon, 26 Nov 2018 17:17:54 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa , freebsd-stable@freebsd.org, Konstantin Belousov 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> <1f170eba-33de-0c79-9e6f-d18d5199e9fe@sentex.net> From: Pete French Message-ID: <2b0a776b-e5a8-ecfc-14f1-422d7b572720@ingresso.co.uk> Date: Mon, 26 Nov 2018 17:18:00 +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: <1f170eba-33de-0c79-9e6f-d18d5199e9fe@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: AC1637DBC8 X-Spamd-Result: default: False [3.68 / 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)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2a02:b90:3002:411::3]; RCVD_TLS_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(0.23)[0.227,0]; RDNS_NONE(1.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.27)[0.269,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: ingresso-co-uk.mail.protection.outlook.com]; DMARC_POLICY_ALLOW(-0.50)[ingresso.co.uk,none]; NEURAL_SPAM_LONG(0.52)[0.516,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 17:17:56 -0000 On 26/11/2018 16:30, Mike Tancsa wrote: > Interesting, I too have noticed my one test box have the odd lockup.  I > think it started around the BETA series. Is it possible something > "undid" one of the fixes ? I brought the box in question upto > 12.0-PRERELEASE FreeBSD 12.0-PRERELEASE r340724 and its been fine for 5 > days. Sadly, when it was locking up (no panic, just a solid lockup) it > took some random amount of time and generally did not matter if the box > was loaded or not. Same with mine loading seesm immaterial - I am running r340430 on mine. Will update when I am can, though am slightly reuctant to do remotely as if the reboot fails I then need to get on a train and go fix it ;) thanks, -pete.