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.
On 1/22/2018 1:25 PM, 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.We use go quite a bit on one customer app and its quite stable. But thats a FreeBSD RELENG_10 box on an intel chip. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike at sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/
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.