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, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ _______________________________________________ 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"
