From owner-freebsd-stable@freebsd.org Tue Dec 4 15:42:08 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 C2FC0131069B for ; Tue, 4 Dec 2018 15:42:08 +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 DC7DA7E553; Tue, 4 Dec 2018 15:42:07 +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 1gUCpn-000LO8-9a; Tue, 04 Dec 2018 15:42:03 +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> <276df722-7c6c-00c2-69ca-87efafac0448@sentex.net> From: Pete French Message-ID: <2c2657b6-8ef4-7741-c09d-b760d3ecc058@ingresso.co.uk> Date: Tue, 4 Dec 2018 15:42:02 +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: <276df722-7c6c-00c2-69ca-87efafac0448@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: DC7DA7E553 X-Spamd-Result: default: False [2.97 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(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.70)[0.695,0]; RDNS_NONE(1.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[ingresso-co-uk.mail.protection.outlook.com,ingresso-co-uk.mail.protection.outlook.com]; DMARC_POLICY_ALLOW(-0.50)[ingresso.co.uk,none]; NEURAL_SPAM_LONG(0.41)[0.407,0]; NEURAL_HAM_MEDIUM(-0.81)[-0.806,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]; MID_RHS_MATCH_FROM(0.00)[]; HFILTER_HOSTNAME_UNKNOWN(2.50)[]; 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: Tue, 04 Dec 2018 15:42:08 -0000 On 04/12/2018 15:04, Mike Tancsa wrote: > Well, another lockup. This time after ~ 10 days of uptime. Box was idle > at the time and just a solid freeze. This is an ASUS PRIME X370-PRO > running BIOS from 09/07/2018 (latest).  Not sure if BIOS related or OS > related. I have another motherboard (MSI) that I will install 12.0 on > and see if its any different.  There is also a micro code update from > AMD last week. However, there are no release notes as to what it > changes. I will hold off on that for now and see if I can get lockups on > the MSI in the next week or two. I did the opposite yesterday - I updated my microcode to the latest one from MSI (though the AMD update it contains is from the summer I belive, depsite the BIOS only comming out a couple of weeks ago). Am running 12-STABLE on there, and will see how long it lasts. Only got to do this yesterday as havent been near the machine for weeks. I didnt adjust any RAM timings and left everything at the default after the BIOS update. but until yesterday it has locked up about every couple of days :-( -pete.