From owner-freebsd-stable@freebsd.org Tue Jan 23 10:16:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 281C8EC89AA for ; Tue, 23 Jan 2018 10:16:52 +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 C016772CF2; Tue, 23 Jan 2018 10:16:51 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from cpc73666-dals20-2-0-cust303.20-2.cable.virginm.net ([82.47.237.48] helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1edvdD-00088M-Gj; Tue, 23 Jan 2018 10:16:43 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> From: Pete French Message-ID: Date: Tue, 23 Jan 2018 10:17:06 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit 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: Tue, 23 Jan 2018 10:16:52 -0000 On 22/01/2018 18:25, Don Lewis wrote: > On 22 Jan, Pete French wrote: >> >> >> On 21/01/2018 19:05, Peter Moody wrote: >>> hm, so i've got nearly 3 days of uptime with smt disabled. >>> unfortunately this means that my otherwise '12' cores is actually only >>> '6'. I'm also getting occasional segfaults compiling go programs. >> >> Isn't go known to have issues on BSD anyway though ? I have seen >> complaints of random crashes running go under BSD systems - and >> preseumably the go compiler itself is written in go, so those issues >> might surface when compiling. > > Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't > recall any unexpected go crashes and I haven't seen problems building > go on my older AMD machines. From the go 1.9 release notes: "Known Issues There are some instabilities on FreeBSD that are known but not understood. These can lead to program crashes in rare cases. See issue 15658. Any help in solving this FreeBSD-specific issue would be appreciated." ( link is to https://github.com/golang/go/issues/15658 ) Having said that, we use it internally and have not seen any issues with it ourselves. Just I am wary of the release notes, and that issue report.