Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Jan 2018 12:48:23 -0800
From:      Peter Moody <freebsd@hda3.com>
To:        Mike Tancsa <mike@sentex.net>
Cc:        Nimrod Levy <nimrodl@gmail.com>, Don Lewis <truckman@freebsd.org>, freebsd-stable@freebsd.org, Pete French <petefrench@ingresso.co.uk>
Subject:   Re: Ryzen issues on FreeBSD ?
Message-ID:  <CADbMJxm5j%2B3WO06jV1wQ5TYEA8rA4E0CBT4ZCNuwYHAk7Gt7cg@mail.gmail.com>
In-Reply-To: <b709107e-0d05-6e81-c960-bd92ddc40860@sentex.net>
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> <CADbMJxm308Pv1OsSj58WVBnM4oYNy8SeQxn54XNt3w0_zaZVFg@mail.gmail.com> <b709107e-0d05-6e81-c960-bd92ddc40860@sentex.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 19, 2018 at 12:39 PM, Mike Tancsa <mike@sentex.net> 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
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADbMJxm5j%2B3WO06jV1wQ5TYEA8rA4E0CBT4ZCNuwYHAk7Gt7cg>