Date: Sun, 28 Jan 2018 16:41:11 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: Mike Tancsa <mike@sentex.net> Cc: Peter Moody <freebsd@hda3.com>, Pete French <petefrench@ingresso.co.uk>, freebsd-stable@freebsd.org, Andriy Gapon <avg@freebsd.org> Subject: Re: Ryzen issues on FreeBSD ? Message-ID: <tkrat.e541d1b83f4f6c75@FreeBSD.org> In-Reply-To: <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <tkrat.5ec856810e0c7ced@FreeBSD.org> <CAMgUhpqZyCOjqVhMCAi-b_JaKYtyfqDf0pOcX0LwV2dcTuusyg@mail.gmail.com> <CAMgUhpqpYpoi1bD9h_SYvh83g_Csky%2BqMkTsOYZ1zcHYxtMeHg@mail.gmail.com> <dd29d77a-deb9-423e-f9b8-cb07387bbfd5@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 Jan, Mike Tancsa wrote: > On 1/27/2018 3:23 AM, Don Lewis wrote: >> >> I just ran into this for this first time with samba46. I kicked of a >> ports build this evening before leaving for several hours. When I >> returned, samba46 had failed with a build runaway. I just tried again >> and I see python stuck in the usem state. This is what I see with >> procstat -k: > > Hmmm, is this indicative of a processor bug or a FreeBSD bug or its > indeterminate at this point ? My suspicion is a FreeBSD bug, probably a locking / race issue. I know that we've had to make some tweeks to our code for AMD CPUs, like this: ------------------------------------------------------------------------ r321608 | kib | 2017-07-27 01:37:07 -0700 (Thu, 27 Jul 2017) | 9 lines Use MFENCE to serialize RDTSC on non-Intel CPUs. Kernel already used the stronger barrier instruction for AMDs, correct the userspace fast gettimeofday() implementation as well. I did go back and look at the build runaways that I've occasionally seen on my AMD FX-8320E package builder. I haven't seen the python issue there, but have seen gmake get stuck in a sleeping state with a bunch of zombie offspring.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.e541d1b83f4f6c75>