On Sat, 07 Mar 2009 09:10:08 +0200, Giorgos Keramidas <keram...@ceid.upatras.gr> wrote: > "umtx lock", "umtx", "umtxn", "umtxpi" and "umtxpp" are internal kernel > strings that are used to identify particular locks and wait conditions > where a process may block while running inside the kernel.
Okay, this makes things more clear to me. > A recent FreeBSD 8.0-CURRENT kernel shows: [...] Having a look at various source files makes me believe that the problem described has something to do with memory access of Opera "through" the kernel (mutex -> mtx). It furthermore explains the "hanging" - a sleep command in the kernel. For the "uncond" state, I found nothing as informative as the above. Maybe it's a "don't know" placeholder. :-) PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 9774 poly 3 101 0 145M 115M ucond 0:00 11.08% opera Furthermore, I think top(1) gets the text for the locks from somewhere else, they're not part of the top(1) sources. At least, /usr/src/usr.bin/top is very dry and doesn't contain much more when in /usr/obj. :-) -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
