freebsd stable - Apr 2018 - Ryzen issues on FreeBSD ? (with sort of workaround)

To be honest, I can't remember for certain what's set in the BIOS right
now. The last post I made was from 3/17 and it says I have the memory clock
lowered and c-states disabled. I don't think I've changed anything but
the
build of stable since then.

--
Nimrod

On Fri, Apr 20, 2018 at 7:55 AM Pete French <petefrench at ingresso.co.uk>
wrote:
>
>
> On 20/04/2018 12:48, Nimrod Levy wrote:
> > I'm really glad to see that I'm not the only one still
interested in
> > this thread.  I don't really have anything new to contribute.
I've been
> > getting about a week or so uptime out of my box. My habit has been to
> > see if it hangs, then reboot and rebuild latest stable and reboot and
> > run that for a while. Although now that this thread pops back up, I
just
> > realized it's been 2 weeks since the last cycle. I don't trust
it yet,
> > but I've seen clear improvement since this started.
>
> What setting sdo you have - just the ones I listed or some in the BSD
> setup itself ? I am surprised that the operson who said they were
> getting an actual Epyc server hasn't commented again on the thread.
> Hopefully that means it works fine on the server hardware :-)
>
> I have seen a few commits go through in STABLE related to VM which
> interest me, and which might cause hangs, so we shall see how it goes.
> Possibly looking at the Ryzen issue has flushed out a few VM problems
> anyway, which would be good, as more stbaility is always good (and I
> have a vague hope it might fix the mysetrious Go hangs too).
>
> -pete.
>
-- 

--
Nimrod

Its not just the Ryzen, I can lock up Epyc CPUs as well. They take a bit
longer, but its not that hard to repeat. Unfortunately, I had to
allocate this hardware over the Linux where it works reliably under all
workloads without any such lock ups with all the default BIOS settings :(

Here is a test case.
https://lists.freebsd.org/pipermail/freebsd-stable/2018-February/088433.html

Peter was able to recreate it as well.

https://lists.freebsd.org/pipermail/freebsd-virtualization/2018-March/006187.html

I dont think its VM / virtualization per se.  I think Peter mentioned
something about IPIs

	---Mike



On 4/20/2018 8:39 AM, Nimrod Levy wrote:
> To be honest, I can't remember for certain what's set in the BIOS
right
> now. The last post I made was from 3/17 and it says I have the memory clock
> lowered and c-states disabled. I don't think I've changed anything
but the
> build of stable since then.
> 
> --
> Nimrod
> 
> On Fri, Apr 20, 2018 at 7:55 AM Pete French <petefrench at
ingresso.co.uk>
> wrote:
> 
>>
>>
>> On 20/04/2018 12:48, Nimrod Levy wrote:
>>> I'm really glad to see that I'm not the only one still
interested in
>>> this thread.  I don't really have anything new to contribute.
I've been
>>> getting about a week or so uptime out of my box. My habit has been
to
>>> see if it hangs, then reboot and rebuild latest stable and reboot
and
>>> run that for a while. Although now that this thread pops back up, I
just
>>> realized it's been 2 weeks since the last cycle. I don't
trust it yet,
>>> but I've seen clear improvement since this started.
>>
>> What setting sdo you have - just the ones I listed or some in the BSD
>> setup itself ? I am surprised that the operson who said they were
>> getting an actual Epyc server hasn't commented again on the thread.
>> Hopefully that means it works fine on the server hardware :-)
>>
>> I have seen a few commits go through in STABLE related to VM which
>> interest me, and which might cause hangs, so we shall see how it goes.
>> Possibly looking at the Ryzen issue has flushed out a few VM problems
>> anyway, which would be good, as more stbaility is always good (and I
>> have a vague hope it might fix the mysetrious Go hangs too).
>>
>> -pete.
>>

-- 
-------------------
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, mike at sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada