Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Jan 2018 10:15:10 -0800 (PST)
From:      Don Lewis <truckman@FreeBSD.org>
To:        Pete French <petefrench@ingresso.co.uk>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Ryzen issues on FreeBSD ?
Message-ID:  <tkrat.7ec3b3b4964a2db2@FreeBSD.org>
In-Reply-To: <a1ad31b5-7152-38b0-6721-b85977ce3448@ingresso.co.uk>
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%2B5HeBi1MRegs=XoKpdHW8-i%2Bec0k-DNaL_pcN6PCPKw@mail.gmail.com> <tkrat.5ec856810e0c7ced@FreeBSD.org> <CAMgUhpqZyCOjqVhMCAi-b_JaKYtyfqDf0pOcX0LwV2dcTuusyg@mail.gmail.com> <CAMgUhpqpYpoi1bD9h_SYvh83g_Csky%2BqMkTsOYZ1zcHYxtMeHg@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%2Biq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com> <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC%2BD9fddENPiiFng@mail.gmail.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <tkrat.8fa97919286143d7@FreeBSD.org> <a1ad31b5-7152-38b0-6721-b85977ce3448@ingresso.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
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.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.7ec3b3b4964a2db2>