From owner-freebsd-threads@FreeBSD.ORG Mon May 19 11:07:01 2008 Return-Path: Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79ADF106564A for ; Mon, 19 May 2008 11:07:01 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 60AEC8FC2B for ; Mon, 19 May 2008 11:07:01 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m4JB71mC011748 for ; Mon, 19 May 2008 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m4JB70XE011744 for freebsd-threads@FreeBSD.org; Mon, 19 May 2008 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 May 2008 11:07:00 GMT Message-Id: <200805191107.m4JB70XE011744@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-threads@FreeBSD.org X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 11:07:01 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s threa/76690 threads fork hang in child for -lc_r 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL s bin/32295 threads pthread dont dequeue signals s threa/34536 threads accept() blocks other threads s threa/39922 threads [threads] [patch] Threaded applications executed with s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under s threa/49087 threads Signals lost in programs linked with libc_r o threa/70975 threads [sysvipc] unexpected and unreliable behaviour when usi o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST o threa/75273 threads FBSD 5.3 libpthread (KSE) bug o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag s threa/76694 threads fork cause hang in dup()/close() function in child (-l o threa/79683 threads svctcp_create() fails if multiple threads call at the o threa/80435 threads panic on high loads o threa/83914 threads [libc] popen() doesn't work in static threaded program s threa/84483 threads problems with devel/nspr and -lc_r on 4.x s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r o threa/101323 threads fork(2) in threaded programs broken. o threa/103975 threads Implicit loading/unloading of libpthread.so may crash o threa/110636 threads [request] gdb(1): using gdb with multi thread applicat o threa/118715 threads kse problem o threa/121336 threads lang/neko threading ok on UP, broken on SMP (FreeBSD 7 23 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s threa/30464 threads pthread mutex attributes -- pshared s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra s threa/40671 threads pthread_cancel doesn't remove thread from condition qu s threa/69020 threads pthreads library leaks _gc_mutex o threa/79887 threads [patch] freopen() isn't thread-safe o threa/80992 threads abort() sometimes not caught by gdb depending on threa o threa/110306 threads apache 2.0 segmentation violation when calling gethost o threa/115211 threads pthread_atfork misbehaves in initial thread o threa/116181 threads /dev/io-related io access permissions are not propagat o threa/116668 threads can no longer use jdk15 with libthr on -stable SMP o threa/122923 threads 'nice' does not prevent background process from steali 11 problems total. From owner-freebsd-threads@FreeBSD.ORG Fri May 23 07:09:40 2008 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF5421065679 for ; Fri, 23 May 2008 07:09:40 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6DFFF8FC28 for ; Fri, 23 May 2008 07:09:40 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JzRPH-0003gH-AV for freebsd-threads@freebsd.org; Fri, 23 May 2008 10:09:39 +0300 Message-ID: <48366DAB.2000200@icyb.net.ua> Date: Fri, 23 May 2008 10:09:31 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: freebsd-threads@freebsd.org References: <48299715.8010303@icyb.net.ua> In-Reply-To: <48299715.8010303@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: RELENG_7 libthr: _umtx_op -1 errno 60 Operation timed out X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 07:09:40 -0000 on 13/05/2008 16:26 Andriy Gapon said the following: > I observe the following issue with some programs (e.g. firefox) from > time. A completely idle program suddenly starts using a lot of CPU and > sometimes memory too. For example, minimized firefox with no pages open. > Restarting the program make the behavior go away. > On one such occasion I ran ktrace on firefox and I saw a lot of messages > like the following in kdump: > 13974 firefox-bin RET _umtx_op -1 errno 60 Operation timed out > Attaching with gdb I also saw a quite strange stack (unfortunately > firefox and the libs are without debug). I didn't save it but it looked > something like the following: > __error() > ?? > ?? > pthread_cond_init() > ?? > > I wonder what could be a cause of this. > Could it be some sort of resource limitation? Here is more details from userland part. I re-built libthr with debugging and here's a typical stack trace for the described above condition: 0x28ad26b3 in _umtx_op_err () at /system/src/lib/libthr/arch/i386/i386/_umtx_op_err.S:36 36 SYSCALL_ERR(_umtx_op) (gdb) bt #0 0x28ad26b3 in _umtx_op_err () at /system/src/lib/libthr/arch/i386/i386/_umtx_op_err.S:36 #1 0x28ad22bd in _thr_ucond_wait (cv=0x8209860, m=0x8209840, timeout=0x0, check_unparking=1) at /system/src/lib/libthr/thread/thr_umtx.c:129 #2 0x28ad0609 in cond_wait_common (cond=0x8208108, mutex=0x820810c, abstime=0x0, cancel=1) at /system/src/lib/libthr/thread/thr_cond.c:204 #3 0x28ad06e8 in __pthread_cond_wait (cond=0x8208108, mutex=0x820810c) at /system/src/lib/libthr/thread/thr_cond.c:228 I am a newbie in this area - what is the difference between _pthread_cond_wait and __pthread_cond_wait? And _X vs __X in general? -- Andriy Gapon From owner-freebsd-threads@FreeBSD.ORG Fri May 23 07:28:28 2008 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA9BC106568F for ; Fri, 23 May 2008 07:28:28 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 9B4A08FC21 for ; Fri, 23 May 2008 07:28:28 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost ([127.0.0.1] helo=edge.pp.kiev.ua) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JzRhT-0004Qx-G3 for freebsd-threads@freebsd.org; Fri, 23 May 2008 10:28:27 +0300 Message-ID: <4836721A.1030402@icyb.net.ua> Date: Fri, 23 May 2008 10:28:26 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.12 (X11/20080320) MIME-Version: 1.0 To: freebsd-threads@freebsd.org References: <48299715.8010303@icyb.net.ua> <48366DAB.2000200@icyb.net.ua> In-Reply-To: <48366DAB.2000200@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: RELENG_7 libthr: _umtx_op -1 errno 60 Operation timed out X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 07:28:28 -0000 on 23/05/2008 10:09 Andriy Gapon said the following: > on 13/05/2008 16:26 Andriy Gapon said the following: >> I observe the following issue with some programs (e.g. firefox) from >> time. A completely idle program suddenly starts using a lot of CPU and >> sometimes memory too. For example, minimized firefox with no pages open. >> Restarting the program make the behavior go away. >> On one such occasion I ran ktrace on firefox and I saw a lot of messages >> like the following in kdump: >> 13974 firefox-bin RET _umtx_op -1 errno 60 Operation timed out >> Attaching with gdb I also saw a quite strange stack (unfortunately >> firefox and the libs are without debug). I didn't save it but it looked >> something like the following: >> __error() >> ?? >> ?? >> pthread_cond_init() >> ?? >> >> I wonder what could be a cause of this. >> Could it be some sort of resource limitation? > > Here is more details from userland part. > I re-built libthr with debugging and here's a typical stack trace for > the described above condition: > 0x28ad26b3 in _umtx_op_err () at > /system/src/lib/libthr/arch/i386/i386/_umtx_op_err.S:36 > 36 SYSCALL_ERR(_umtx_op) > (gdb) bt > #0 0x28ad26b3 in _umtx_op_err () at > /system/src/lib/libthr/arch/i386/i386/_umtx_op_err.S:36 > #1 0x28ad22bd in _thr_ucond_wait (cv=0x8209860, m=0x8209840, > timeout=0x0, check_unparking=1) at > /system/src/lib/libthr/thread/thr_umtx.c:129 > #2 0x28ad0609 in cond_wait_common (cond=0x8208108, mutex=0x820810c, > abstime=0x0, cancel=1) at /system/src/lib/libthr/thread/thr_cond.c:204 > #3 0x28ad06e8 in __pthread_cond_wait (cond=0x8208108, mutex=0x820810c) > at /system/src/lib/libthr/thread/thr_cond.c:228 oops, sorry, the above stack trace is for a good program in cond_wait. I'll try to get one for a program in a bad state once I get it. > I am a newbie in this area - what is the difference between > _pthread_cond_wait and __pthread_cond_wait? And _X vs __X in general? > -- Andriy Gapon