From owner-freebsd-stable@freebsd.org Tue Jan 23 18:15:24 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 DC3C4EBE0CC for ; Tue, 23 Jan 2018 18:15:24 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B481163B8A for ; Tue, 23 Jan 2018 18:15:24 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w0NIFnfg095285 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 23 Jan 2018 18:15:50 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w0NIFF82037616 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jan 2018 10:15:16 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Tue, 23 Jan 2018 10:15:10 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Pete French cc: freebsd-stable@freebsd.org In-Reply-To: Message-ID: 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE 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 18:15:25 -0000 On 23 Jan, Pete French wrote: > 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. Interesting ... I've only seen problems on my Ryzen machine, which has >= 2x the number of cores as any of my other machines. All are AMD CPUs.