fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the
hw.lower_amd64_sharedpage setting to my loader.conf and got a crash
last night following the familiar high load -> idle. this was with SMT
re-enabled. no crashdump, so it was the hard crash that I've been
getting.
all of the builds that had been failing before were fine; net/samba47,
lang/ghc (though hadn't actually done this before to verify that it
failed on my rig), so that's at least a plus. The only other
out-of-the-ordinary thing I was doing at the time was that I'd started
a zpool scrub. That succeeded fine the day before when SMT was
disabled.
shrug, I'm at a loss here.
On Mon, Jan 22, 2018 at 10:32 AM, Mike Tancsa <mike at sentex.net>
wrote:> 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/
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"