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) ---Mike
On Fri, Jan 19, 2018 at 12:39 PM, Mike Tancsa <mike at 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 >
On 19 Jan, 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)I never seen the idle lockup problem here. Prior to the shared page fix, I could almost always trigger a system hang or silent reboot by doing a parallel build of openjdk8.