Date: Mon, 12 Feb 2018 20:48:56 -0500 From: Mike Tancsa <mike@sentex.net> To: Don Lewis <truckman@FreeBSD.org>, Eugene Grosbein <eugen@grosbein.net> Cc: freebsd-stable@freebsd.org, Peter Moody <freebsd@hda3.com>, Andriy Gapon <avg@freebsd.org>, Pete French <petefrench@ingresso.co.uk> Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Message-ID: <73f83421-97ed-88f8-08be-39cf5a70ed20@sentex.net> In-Reply-To: <tkrat.7fad2b76b85bc4b1@FreeBSD.org> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <a601973f-9205-8dd9-7f78-a7f03985ab4a@sentex.net> <CAMgUhpop3=J7TQimK2iHdGTc=hnTgCEZDqibDSRCyTPMWX5wJQ@mail.gmail.com> <CAMgUhpop54hJ%2Biq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com> <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC%2BD9fddENPiiFng@mail.gmail.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <tkrat.8fa97919286143d7@FreeBSD.org> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <CADbMJxkRR8s1=WWXP%2BH9eOHv_UWMQrUR=_E4aFw91VCeep82pw@mail.gmail.com> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <tkrat.975666e9f483a6a0@FreeBSD.org> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <tkrat.ada77e0420783bed@FreeBSD.org> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <tkrat.e541d1b83f4f6c75@FreeBSD.org> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <c0319297-d47d-449d-a6f1-2529d1d38541@sentex.net> <5A71C5AE.6020202@grosbein.net> <tkrat.7fad2b76b85bc4b1@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/12/2018 4: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 > > Since applying that patch, I did three poudriere runs to build the set > of ~1700 ports that I use. Other than one gmake-related build runaway > that I've also seen on my AMD FX-8320E, I didn't see any random port > build failures. When I was last did some testing a few weeks ago, > lang/go would almost always fail. I also would seem random build > failures in lang/guile or finance/gnucash (which uses guile during its > build) on both my Ryzen and FX-8320E machines, but those built cleanly > all three times. > > I even built samba 16 times in a row without a hang. > Cool! I will give it a try! In other news, the latest BIOS patch from ASUS for my motherboard *seems* to have fixed the random hangs. In the BIOS, I had to dial down the memory one notch, disable q-states and disable core boost for my non X Ryzen CPUs. I did that Friday, and running a load that would typically lock up the box, survived the weekend. Same with the box I have in Zoo. No random freeze ups. I was also able to take the amdtemp and amdsmn code from HEAD and compile it on STABLE to confirm the CPU is / was not overheating. Peak temp in the low 50s even with the CPU cores are all maxed out. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?73f83421-97ed-88f8-08be-39cf5a70ed20>