From owner-freebsd-stable@freebsd.org  Mon Jan 22 11:48:19 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
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 69200EBC2D9
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon, 22 Jan 2018 11:48:19 +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 3116D783AD
 for <freebsd-stable@freebsd.org>; Mon, 22 Jan 2018 11:48:18 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6])
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>) id 1edaaF-000Je9-Eb
 for freebsd-stable@freebsd.org; Mon, 22 Jan 2018 11:48:15 +0000
Subject: Re: Ryzen issues on FreeBSD ?
To: 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>
 <tkrat.6d8f44d87e74fa14@FreeBSD.org>
 <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net>
 <CAMgUhpr+5HeBi1MRegs=XoKpdHW8-i+ec0k-DNaL_pcN6PCPKw@mail.gmail.com>
 <tkrat.5ec856810e0c7ced@FreeBSD.org>
 <CAMgUhpqZyCOjqVhMCAi-b_JaKYtyfqDf0pOcX0LwV2dcTuusyg@mail.gmail.com>
 <CAMgUhpqpYpoi1bD9h_SYvh83g_Csky+qMkTsOYZ1zcHYxtMeHg@mail.gmail.com>
 <dd29d77a-deb9-423e-f9b8-cb07387bbfd5@sentex.net>
 <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com>
 <a601973f-9205-8dd9-7f78-a7f03985ab4a@sentex.net>
 <CAMgUhpop3=J7TQimK2iHdGTc=hnTgCEZDqibDSRCyTPMWX5wJQ@mail.gmail.com>
 <CAMgUhpop54hJ+iq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com>
 <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC+D9fddENPiiFng@mail.gmail.com>
From: Pete French <petefrench@ingresso.co.uk>
Message-ID: <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk>
Date: Mon, 22 Jan 2018 11:48:15 +0000
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC+D9fddENPiiFng@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2018 11:48:19 -0000



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.