Date: Sat, 27 Jan 2018 11:52:16 -0500 From: Mike Tancsa <mike@sentex.net> To: Don Lewis <truckman@FreeBSD.org> 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: <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> In-Reply-To: <tkrat.ada77e0420783bed@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 ? > > PID TID COMM TDNAME KSTACK > 90692 100801 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100824 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100857 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100956 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100995 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101483 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101538 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101549 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101570 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101572 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101583 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101588 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101593 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101610 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101629 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_lock_umutex __umtx_op_wait_umutex amd64_syscall fast_syscall_common > 90692 101666 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 102114 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > > and procstat -t: > > PID TID COMM TDNAME CPU PRI STATE WCHAN > 90692 100801 python2.7 - -1 124 sleep usem > 90692 100824 python2.7 - -1 124 sleep usem > 90692 100857 python2.7 - -1 124 sleep usem > 90692 100956 python2.7 - -1 125 sleep usem > 90692 100995 python2.7 - -1 124 sleep usem > 90692 101483 python2.7 - -1 124 sleep usem > 90692 101538 python2.7 - -1 125 sleep usem > 90692 101549 python2.7 - -1 124 sleep usem > 90692 101570 python2.7 - -1 124 sleep usem > 90692 101572 python2.7 - -1 124 sleep usem > 90692 101583 python2.7 - -1 125 sleep usem > 90692 101588 python2.7 - -1 124 sleep usem > 90692 101593 python2.7 - -1 123 sleep usem > 90692 101610 python2.7 - -1 124 sleep usem > 90692 101629 python2.7 - -1 125 sleep umtxn > 90692 101666 python2.7 - -1 124 sleep usem > 90692 102114 python2.7 - -1 152 sleep usem > > The machine isn't totally idle. The last pid value in top increases by > about 40 every two seconds. Looks like it might be poudriere polling > something ... > > > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55913e41-3a8a-9a4d-6862-e09a3d0f4d55>