If you want to use an operating system that takes advantage of CPU to memory optimizations without taking steps backwards you have to pay a price.
Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: Don Lewis <truck...@freebsd.org> Date: 1/30/18 4:58 PM (GMT-08:00) To: Mike Tancsa <m...@sentex.net> Cc: Pete French <petefre...@ingresso.co.uk>, freebsd-stable@freebsd.org, Andriy Gapon <a...@freebsd.org>, Peter Moody <free...@hda3.com>, Nimrod Levy <nimr...@gmail.com> Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) On 30 Jan, Mike Tancsa wrote: > On 1/30/2018 5:23 PM, Nimrod Levy wrote: >> That's really strange. I never saw those kinds of deadlocks, but I did >> notice that if I kept the cpu busy using distributed.net >> <http://distributed.net> I could keep the full system lockups away for >> at least a week if not longer. >> >> Not to keep harping on it, but what worked for me was lowering the >> memory speed. I'm at 11 days of uptime so far without anything running >> the cpu. Before the change it would lock up anywhere from an hour to a day. >> > Spoke too soon. After a dozen loops, the process has hung again. Note, > this is not the box locking up, just the compile. I do have memory at a > lower speed too. -- 2133 instead of the default 2400 I suspect the problem is a race condition that causes a wakeup to be lost. Adding load changes the timing enough to avoid the problem most of the time. > I also just tried upgrading to the latest HEAD with a generic kernel and > same / similar lockups although procstat -kk gives some odd results > > > root@amdtestr12:/home/mdtancsa # procstat -kk 6067 > PID TID COMM TDNAME KSTACK > > 6067 100865 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100900 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100901 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100902 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100903 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100904 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100905 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100906 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100907 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100908 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100909 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100910 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > 6067 100911 python2.7 - ??+0 ??+0 ??+0 ??+0 > ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 Strange ... kernel vs. world mismatch? Some other new regression in HEAD? _______________________________________________ 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"
