Re: Ryzen consensus

[Peter Moody]

I've had no issues with my r7 1700 for a while now. updated my bios
(msi x370) probably 2 months ago and i'm currently running 11.2-STABLE
r336329

On Sat, Jul 21, 2018 at 6:48 PM, George Mitchell  wrote:
> Based on people's recent Ryzen experiences, is it fair to say that
> FreeBSD 11.2 is now believed to work on Ryzens, if you have a recent
> enough Ryzen and your motherboard has been updated to the latest BIOS?
> -- George
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: problems with ssh-agent after running MATE desktop

[Peter Moody]

On Thu, May 24, 2018 at 9:01 AM, Charlie Li  wrote:

> MATE loads all of gnome-keyring, including the ssh-agent portion.

neither here nor there, but gnome-keyring is bad at being an
ssh-agent. if you can in any way avoid it, your life will be better if
you do.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

[Peter Moody]

On Mon, Feb 12, 2018 at 1:49 PM, Don Lewis  wrote:
> On 31 Jan, Eugene Grosbein wrote:
>> 31.01.2018 4:36, Mike Tancsa пишет:
>>> On 1/30/2018 2:51 PM, Mike Tancsa wrote:

 And sadly, I am still able to hang the compile in about the same place.
 However, if I set
>>>
>>>
>>> OK, here is a sort of work around. If I have the box a little more busy,
>>> I can avoid whatever deadlock is going on.  In another console I have
>>> cat /dev/urandom | sha256
>>> running while the build runs
>>>
>>> ... and I can compile net/samba47 from scratch without the compile
>>> hanging.  This problem also happens on HEAD from today.  Should I start
>>> a new thread on freebsd-current ? Or just file a bug report ?
>>> The compile worked 4/4
>>
>> That's really strange. Could you try to do "sysctl 
>> kern.eventtimer.periodic=1"
>> and re-do the test without extra load?
>
> I'm having really good luck with the kernel patch attached to this
> message:
> https://docs.freebsd.org/cgi/getmsg.cgi?fetch=417183+0+archive/2018/freebsd-hackers/20180211.freebsd-hackers

I'm new to this; what are the chances that this gets into -STABLE in
the near future?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

[Peter Moody]

to close the loop on this thread (for me at least); I replaced the
asrock ab350 with an msi x370 and things now, just work (c). the msi
detects the memory as 2133 (rather than the 3000 mhz it was sold as).
i'm not sure if this because it really is 2133 mhz, or because the msi
just likes that frequency better. i'm also not sure to what extent the
issue was fixed by the slower memory versus the different mobo brand &
chipset.

now my only issue is crashes when I scrub my zfs pool, though I
strongly suspect a dying disk is the cause of that.

Cheers,
peter


On Thu, Feb 1, 2018 at 10:51 AM, Mike Tancsa  wrote:
> On 2/1/2018 1:49 PM, Mike Tancsa wrote:
>> On 2/1/2018 1:40 PM, Ed Maste wrote:
 root@amdtestr12:/home/mdtancsa # procstat -kk 6067
   PIDTID COMMTDNAME  KSTACK

  6067 100865 python2.7   -   ??+0 ??+0 ??+0 ??+0
 ??+0 ??+0 ??+0 ??+0 ??+0 ??+0
>>>
>>> I think this part is due to the broken loader change in r328536.
>>> Kernel symbol loading is broken, and this in particular isn't related
>>> to Ryzen issues.
>>
>> Just for the archives, after a buildworld to a newer rev of the source
>> tree, all was good :)
> Ugh, to clarify, all was good with the procstat issue.
>
> ---Mike
>
>
> --
> ---
> Mike Tancsa, tel +1 519 651 3400 x203
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

> Gigabyte AX370 Gaming 5.

all of issues so far have been on a pair of asrock ab350's. But I've
got an msi x370 coming early next week.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

On Jan 27, 2018 6:20 PM, "Nimrod Levy"  wrote:

I'm about ready to have a party.  My Ryzen 5 1600 has been up for over 8
days so far after changing the memory to a slower speed.  System load
hovers around .3


I couldn't find an easy way to down-speed my memory in the bios :(



On Sat, Jan 27, 2018 at 8:41 PM Peter Moody  wrote:

> Whelp, I replaced the r5 1600x with an r7 1700 (au 1734) and I'm now
> getting minutes of uptime before I hard crash. With smt, without, with c
> states, without, with opcache, without. No difference.
>
> I'm going to try a completely different motherboard next. I think Amazon
> is starting to dislike me.
>
> On Jan 21, 2018 11:05 AM, "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.
>>
>> should I just RMA this beast again?
>>
>> On Sun, Jan 21, 2018 at 5:25 AM, Nimrod Levy  wrote:
>> > almost 2 days uptime with a lower memory clock. still holding my breath,
>> > but this seems promising.
>> >
>> >
>> >
>> > On Fri, Jan 19, 2018 at 4:02 PM Nimrod Levy  wrote:
>> >
>> >> I can try lowering my memory clock and see what happens.  I'm a little
>> >> skeptical because I have been able to run memtest with no errors for
>> some
>> >> time.  I'm glad to give anything a try...
>> >>
>> >>
>> >> On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa  wrote:
>> >>
>> >>> On 1/19/2018 3:23 PM, Ryan Root wrote:
>> >>> > This looks like the QVL list for your MB ->
>> >>> >
>> >>> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-
>> ax370-Gaming5.pdf
>> >>>
>> >>> Its an Asus MB, but the memory I have is in the above PDF list
>> >>>
>> >>> I dont see CT16G4DFD824A, but I do see other crucial products with
>> >>> slower clock speeds. Right now I do have it set to 2133 where as it
>> was
>> >>> 2400 before.
>> >>>
>> >>> ---Mike
>> >>>
>> >>>
>> >>> >
>> >>> >
>> >>> > On 1/19/2018 12:13 PM, Mike Tancsa wrote:
>> >>> >> Drag :( I have mine disabled as well as lowering the RAM freq to
>> 2100
>> >>> >> from 2400.  For me the hangs are infrequent.  Its only been a day
>> and a
>> >>> >> half, so not sure if its gone or I have been "lucky"... Either
>> ways,
>> >>> >> this platform feels way too fragile to deploy on anything :(
>> >>> >>
>> >>> >>  ---Mike
>> >>> >>
>> >>> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
>> >>> >>> Looks like disabling the C- states in the bios didn't change
>> >>> anything.
>> >>> >>>
>> >>> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy > >>> >>> <mailto:nimr...@gmail.com>> wrote:
>> >>> >>>
>> >>> >>> That looks promising. I just found that seeing in the bios and
>> >>> >>> disabled it. I'll see how it runs.
>> >>> >>>
>> >>> >>> Thanks
>> >>> >>>
>> >>> >>>
>> >>> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis > >>> >>> <mailto:truck...@freebsd.org>> wrote:
>> >>> >>>
>> >>> >>> On 17 Jan, Nimrod Levy wrote:
>> >>> >>> > I'm running 11-STABLE from 12/9.  amdtemp works for
>> me.  It
>> >>> >>> also has the
>> >>> >>> > systl indicating that it it has the shared page fix. I'm
>> >>> >>> pretty sure I've
>> >>> >>> > seen the lockups since then.  I'll update to the latest
>> >>> STABLE
>> >>> >>> and see
>> >>> >>> > what  happens.
>> >>> >>> >
>> >>> >>> > One weird thing about my experience is that if I keep
>> >>> >>> 

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

Whelp, I replaced the r5 1600x with an r7 1700 (au 1734) and I'm now
getting minutes of uptime before I hard crash. With smt, without, with c
states, without, with opcache, without. No difference.

I'm going to try a completely different motherboard next. I think Amazon is
starting to dislike me.

On Jan 21, 2018 11:05 AM, "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.
>
> should I just RMA this beast again?
>
> On Sun, Jan 21, 2018 at 5:25 AM, Nimrod Levy  wrote:
> > almost 2 days uptime with a lower memory clock. still holding my breath,
> > but this seems promising.
> >
> >
> >
> > On Fri, Jan 19, 2018 at 4:02 PM Nimrod Levy  wrote:
> >
> >> I can try lowering my memory clock and see what happens.  I'm a little
> >> skeptical because I have been able to run memtest with no errors for
> some
> >> time.  I'm glad to give anything a try...
> >>
> >>
> >> On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa  wrote:
> >>
> >>> On 1/19/2018 3:23 PM, Ryan Root wrote:
> >>> > This looks like the QVL list for your MB ->
> >>> >
> >>> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-
> ax370-Gaming5.pdf
> >>>
> >>> Its an Asus MB, but the memory I have is in the above PDF list
> >>>
> >>> I dont see CT16G4DFD824A, but I do see other crucial products with
> >>> slower clock speeds. Right now I do have it set to 2133 where as it was
> >>> 2400 before.
> >>>
> >>> ---Mike
> >>>
> >>>
> >>> >
> >>> >
> >>> > On 1/19/2018 12:13 PM, Mike Tancsa wrote:
> >>> >> Drag :( I have mine disabled as well as lowering the RAM freq to
> 2100
> >>> >> from 2400.  For me the hangs are infrequent.  Its only been a day
> and a
> >>> >> half, so not sure if its gone or I have been "lucky"... Either ways,
> >>> >> this platform feels way too fragile to deploy on anything :(
> >>> >>
> >>> >>  ---Mike
> >>> >>
> >>> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
> >>> >>> Looks like disabling the C- states in the bios didn't change
> >>> anything.
> >>> >>>
> >>> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy  >>> >>> <mailto:nimr...@gmail.com>> wrote:
> >>> >>>
> >>> >>> That looks promising. I just found that seeing in the bios and
> >>> >>> disabled it. I'll see how it runs.
> >>> >>>
> >>> >>> Thanks
> >>> >>>
> >>> >>>
> >>> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis  >>> >>> <mailto:truck...@freebsd.org>> wrote:
> >>> >>>
> >>> >>> On 17 Jan, Nimrod Levy wrote:
> >>> >>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.
> It
> >>> >>> also has the
> >>> >>> > systl indicating that it it has the shared page fix. I'm
> >>> >>> pretty sure I've
> >>> >>> > seen the lockups since then.  I'll update to the latest
> >>> STABLE
> >>> >>> and see
> >>> >>> > what  happens.
> >>> >>> >
> >>> >>> > One weird thing about my experience is that if I keep
> >>> >>> something running
> >>> >>> > continuously like the distributed.net <
> >>> http://distributed.net>
> >>> >>> client on 6 of 12 possible threads,
> >>> >>> > it keeps the system up for MUCH longer than without.
> This
> >>> is
> >>> >>> a home server
> >>> >>> > and very lightly loaded (one could argue insanely
> >>> overpowered
> >>> >>> for the use
> >>> >>> > case).
> >>> >>>
> >>> >>> Thi

Re: Ryzen issues on FreeBSD ? (summary of 4 issues)

[Peter Moody]

> I currently have a Ryzen 1600X from week 17/30, which suggests it will
> have the bug. Unfortunately, I don't have it built into a system yet
> as I'm waiting for DDR4 prices to become reasonable again before
> ordering any, so I can't test it.

I've seen the blanking screen lockup on a 1600X from 1739SUS and
1740SUS. Only with SMT enabled though. On the 1739 chip I'm also
seeing cc segfaults on make -j 18 buildworld (again, just with SMT
enabled).

This is all so frustrating.

> I'm not sure how solid this info is, should I RMA it without even
> having tested that it has a problem?
>
> Alban Hertroys
> --
> If you can't see the forest for the trees,
> Cut the trees and you'll see there is no forest.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

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  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, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada   http://www.tancsa.com/
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

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.

should I just RMA this beast again?

On Sun, Jan 21, 2018 at 5:25 AM, Nimrod Levy  wrote:
> almost 2 days uptime with a lower memory clock. still holding my breath,
> but this seems promising.
>
>
>
> On Fri, Jan 19, 2018 at 4:02 PM Nimrod Levy  wrote:
>
>> I can try lowering my memory clock and see what happens.  I'm a little
>> skeptical because I have been able to run memtest with no errors for some
>> time.  I'm glad to give anything a try...
>>
>>
>> On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa  wrote:
>>
>>> On 1/19/2018 3:23 PM, Ryan Root wrote:
>>> > This looks like the QVL list for your MB ->
>>> >
>>> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf
>>>
>>> Its an Asus MB, but the memory I have is in the above PDF list
>>>
>>> I dont see CT16G4DFD824A, but I do see other crucial products with
>>> slower clock speeds. Right now I do have it set to 2133 where as it was
>>> 2400 before.
>>>
>>> ---Mike
>>>
>>>
>>> >
>>> >
>>> > On 1/19/2018 12:13 PM, Mike Tancsa wrote:
>>> >> Drag :( I have mine disabled as well as lowering the RAM freq to 2100
>>> >> from 2400.  For me the hangs are infrequent.  Its only been a day and a
>>> >> half, so not sure if its gone or I have been "lucky"... Either ways,
>>> >> this platform feels way too fragile to deploy on anything :(
>>> >>
>>> >>  ---Mike
>>> >>
>>> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
>>> >>> Looks like disabling the C- states in the bios didn't change
>>> anything.
>>> >>>
>>> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy >> >>> > wrote:
>>> >>>
>>> >>> That looks promising. I just found that seeing in the bios and
>>> >>> disabled it. I'll see how it runs.
>>> >>>
>>> >>> Thanks
>>> >>>
>>> >>>
>>> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis >> >>> > wrote:
>>> >>>
>>> >>> On 17 Jan, Nimrod Levy wrote:
>>> >>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It
>>> >>> also has the
>>> >>> > systl indicating that it it has the shared page fix. I'm
>>> >>> pretty sure I've
>>> >>> > seen the lockups since then.  I'll update to the latest
>>> STABLE
>>> >>> and see
>>> >>> > what  happens.
>>> >>> >
>>> >>> > One weird thing about my experience is that if I keep
>>> >>> something running
>>> >>> > continuously like the distributed.net <
>>> http://distributed.net>
>>> >>> client on 6 of 12 possible threads,
>>> >>> > it keeps the system up for MUCH longer than without.  This
>>> is
>>> >>> a home server
>>> >>> > and very lightly loaded (one could argue insanely
>>> overpowered
>>> >>> for the use
>>> >>> > case).
>>> >>>
>>> >>> This sounds like the problem with the deep Cx states that has
>>> been
>>> >>> reported by numerous Linux users.  I think some motherboard
>>> >>> brands are
>>> >>> more likely to have the problem.  See:
>>> >>>
>>> http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
>>> >>>
>>> >>> --
>>> >>>
>>> >>> --
>>> >>> Nimrod
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>>
>>> >>> --
>>> >>> Nimrod
>>> >>>
>>> >>
>>> >
>>> >
>>> > ___
>>> > freebsd-stable@freebsd.org mailing list
>>> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> > To unsubscribe, send any mail to "
>>> freebsd-stable-unsubscr...@freebsd.org"
>>> >
>>> >
>>>
>>>
>>> --
>>> ---
>>> Mike Tancsa, tel +1 519 651 3400 <(519)%20651-3400>
>>> Sentex Communications, m...@sentex.net
>>> Providing Internet services since 1994 www.sentex.net
>>> Cambridge, Ontario Canada   http://www.tancsa.com/
>>> ___
>>> freebsd-stable@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>>>
>>
>>
>> --
>>
>> --
>> Nimrod
>>
>
>
> --
>
> --
> Nimrod
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

On Fri, Jan 19, 2018 at 1:17 PM, Mike Tancsa  wrote:
> On 1/19/2018 3:48 PM, Peter Moody wrote:
>>
>> weirdly enough though, with SMT enabled, building net/samba47 would
>> always hang (like compilation segfaults). with SMT disabled, no such
>> problems.
>
> wow, thats so strange!  I just tried,and the same thing and see it as well.
>
> [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h
> [ 443/3804] Generating source4/lib/registry/tools/common.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/lib/ldb-samba/ldif_handlers_proto.h"
> ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c
> [ 444/3804] Generating source4/lib/registry/tests/proto.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/source4/lib/registry/tools/common.h"
> ../source4/lib/registry/tools/common.c
>
>
> And it just hangs there. No segfaults, but it just hangs.

yeah whoops, sorry. I had compilation segfaults on my mind b/c of the
linked amd forums posts about gcc segfaults.

anyway, try disabling SMT and see if that helps .. ?

this seems to make parallel stuff perceptibly slower (like a make -j12
buildworld at the same time as make -j 12 in net/samba47), but at this
point I'm just happy with the relative stability.

> A ctrl+t shows just shows
>
> load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
> make: Working in: /usr/ports/net/samba47
>
>
> ---Mike
>
>
>
> --
> ---
> Mike Tancsa, tel +1 519 651 3400
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada   http://www.tancsa.com/
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

On Fri, Jan 19, 2018 at 12:39 PM, Mike Tancsa  wrote:
> On 1/19/2018 3:32 PM, Peter Moody wrote:
>>
>> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about
>> everything in all of these threads; disabling C state (no effect),
>> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking
>> voltage and cooling settings, rma'ing the board the cpu and the
>> memory. nothing helped.
>>
>> last night I tried disabling SMT and, so far so good.
>
>
> Is there anything that can be done to trigger the lockup more reliably ?
> I havent found any patterns. I have had lockups with the system is 100%
> idle and lockups when lightly loaded.  I have yet to see any segfaults
> or sig 11s while doing buildworld (make -j12 or make -j16 even)

"reliably" trigger the lockup, no.

The general pattern was high load followed by low load would lock up;
so a couple 'make -j 32 buildworld' would almost always result in a
lock up a few hours after the last one completes.

weirdly enough though, with SMT enabled, building net/samba47 would
always hang (like compilation segfaults). with SMT disabled, no such
problems.

> ---Mike
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Ryzen issues on FreeBSD ?

[Peter Moody]

On Fri, Jan 19, 2018 at 12:13 PM, Mike Tancsa  wrote:
> Drag :( I have mine disabled as well as lowering the RAM freq to 2100
> from 2400.  For me the hangs are infrequent.  Its only been a day and a
> half, so not sure if its gone or I have been "lucky"... Either ways,
> this platform feels way too fragile to deploy on anything :(
>
> ---Mike
>
> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
>> Looks like disabling the C- states in the bios didn't change anything.

it's too early for me to be 100% certain, but disabling SMT in the
bios has thus far resulted in a more stable system.

I have a ryzen5 1600X and an ASRock AB350M and I've tried just about
everything in all of these threads; disabling C state (no effect),
setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking
voltage and cooling settings, rma'ing the board the cpu and the
memory. nothing helped.

last night I tried disabling SMT and, so far so good.


>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy > > wrote:
>>
>> That looks promising. I just found that seeing in the bios and
>> disabled it. I'll see how it runs.
>>
>> Thanks
>>
>>
>> On Wed, Jan 17, 2018, 18:38 Don Lewis > > wrote:
>>
>> On 17 Jan, Nimrod Levy wrote:
>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It
>> also has the
>> > systl indicating that it it has the shared page fix. I'm
>> pretty sure I've
>> > seen the lockups since then.  I'll update to the latest STABLE
>> and see
>> > what  happens.
>> >
>> > One weird thing about my experience is that if I keep
>> something running
>> > continuously like the distributed.net 
>> client on 6 of 12 possible threads,
>> > it keeps the system up for MUCH longer than without.  This is
>> a home server
>> > and very lightly loaded (one could argue insanely overpowered
>> for the use
>> > case).
>>
>> This sounds like the problem with the deep Cx states that has been
>> reported by numerous Linux users.  I think some motherboard
>> brands are
>> more likely to have the problem.  See:
>> 
>> http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
>>
>> --
>>
>> --
>> Nimrod
>>
>>
>>
>> --
>>
>> --
>> Nimrod
>>
>
>
> --
> ---
> Mike Tancsa, tel +1 519 651 3400
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada   http://www.tancsa.com/
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"