From owner-freebsd-threads@FreeBSD.ORG Mon Mar 7 00:07:13 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8DFC16A4CE for ; Mon, 7 Mar 2005 00:07:13 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A66943D5D for ; Mon, 7 Mar 2005 00:07:13 +0000 (GMT) (envelope-from marcus@FreeBSD.org) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) j2707MbV068050 for ; Sun, 6 Mar 2005 19:07:22 -0500 (EST) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: threads@FreeBSD.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-/wK6AIka2+kmGL5ehLSL" Organization: FreeBSD, Inc. Date: Sun, 06 Mar 2005 19:06:07 -0500 Message-Id: <1110153967.97135.16.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 FreeBSD GNOME Team Port Subject: Request permission to MFC stacksize changes X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2005 00:07:14 -0000 --=-/wK6AIka2+kmGL5ehLSL Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Now that all three threading libraries have had their stacksizes increased, I'd like permission to request re for MFC approval so that these changes get into 5.4-RELEASE. Additionally, I'd like to MFC the libc_r changes back into RELENG_4. I'd be happy to do all the leg work on this if you guys give permission. Thanks. Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-/wK6AIka2+kmGL5ehLSL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCK5rvb2iPiv4Uz4cRAlzJAKCVh25KCj5lE1ItnuANC6X1tY93VQCgrdBE MFVfmFEB4t1sC/VU3Ij2amE= =TraJ -----END PGP SIGNATURE----- --=-/wK6AIka2+kmGL5ehLSL-- From owner-freebsd-threads@FreeBSD.ORG Mon Mar 7 00:58:59 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1696616A4CE; Mon, 7 Mar 2005 00:58:59 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89FE543D4C; Mon, 7 Mar 2005 00:58:58 +0000 (GMT) (envelope-from eischen@mail.ntplx.net) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) j270wvL6020050; Sun, 6 Mar 2005 19:58:57 -0500 (EST) Received: (from eischen@localhost) by sea.ntplx.net (8.11.7p1+Sun/8.11.7) id j270wvP20992; Sun, 6 Mar 2005 19:58:57 -0500 (EST) Date: Sun, 6 Mar 2005 19:58:57 -0500 (EST) From: Daniel Eischen Message-Id: <200503070058.j270wvP20992@sea.ntplx.net> To: marcus@freebsd.org, threads@freebsd.org X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Subject: Re: Request permission to MFC stacksize changes X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2005 00:58:59 -0000 > Now that all three threading libraries have had their stacksizes > increased, I'd like permission to request re for MFC approval so that > these changes get into 5.4-RELEASE. Additionally, I'd like to MFC the > libc_r changes back into RELENG_4. I'd be happy to do all the leg work > on this if you guys give permission. Thanks. OK by me. -- DE From owner-freebsd-threads@FreeBSD.ORG Mon Mar 7 11:01:32 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5967B16A4E3 for ; Mon, 7 Mar 2005 11:01:32 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2548243D31 for ; Mon, 7 Mar 2005 11:01:32 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j27B1WIA037308 for ; Mon, 7 Mar 2005 11:01:32 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j27B1VoS037303 for freebsd-threads@freebsd.org; Mon, 7 Mar 2005 11:01:31 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 7 Mar 2005 11:01:31 GMT Message-Id: <200503071101.j27B1VoS037303@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2005 11:01:32 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/04/22] threads/65883threads libkse's sigwait does not work after fork o [2005/01/26] threads/76690threads fork hang in child for (-lc_r & -lthr) 2 problems total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/07/18] kern/20016 threads pthreads: Cannot set scheduling timer/Can o [2000/08/26] kern/20861 threads libc_r does not honor socket timeouts o [2001/01/20] threads/24472threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] threads/24632threads libc_r delicate deviation from libc in ha o [2001/01/25] kern/24641 threads pthread_rwlock_rdlock can deadlock o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/02/01] threads/34536threads accept() blocks other threads o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/06/27] threads/39922threads [PATCH?] Threaded applications executed w o [2002/08/04] kern/41331 threads Pthread library open sets O_NONBLOCK flag o [2003/03/02] threads/48856threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] threads/49087threads Signals lost in programs linked with libc o [2003/05/08] threads/51949threads thread in accept cannot be cancelled s [2004/03/15] kern/64313 threads FreeBSD (OpenBSD) pthread implicit set/un o [2004/08/26] threads/70975threads unexpected and unreliable behaviour when o [2004/09/14] threads/71725threads Mysql Crashes frequently giving Sock Erro o [2004/10/05] threads/72353threads Assertion fails in /usr/src/lib/libpthrea o [2004/10/07] threads/72429threads threads blocked in stdio (fgets, etc) are o [2004/10/21] threads/72953threads fork() unblocks blocked signals w/o PTHRE o [2004/11/25] threads/74370threads Cannot get lwp 0 registers in gdb o [2004/12/08] threads/74856threads dig/host broken w/ libthr o [2004/12/19] threads/75273threads FBSD 5.3 libpthread (KSE) bug o [2004/12/21] threads/75374threads pthread_kill() ignores SA_SIGINFO flag o [2005/01/04] threads/75795threads applications linked with -lc_r can't clos o [2005/01/26] threads/76694threads fork cause hang in dup()/close() function 25 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/05/26] kern/18824 threads gethostbyname is not thread safe o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything o [2000/10/21] kern/22190 threads A threaded read(2) from a socketpair(2) f o [2001/09/09] threads/30464threads pthread mutex attributes -- pshared o [2002/05/02] threads/37676threads libc_r: msgsnd(), msgrcv(), pread(), pwri s [2002/07/16] threads/40671threads pthread_cancel doesn't remove thread from o [2004/07/13] threads/69020threads pthreads library leaks _gc_mutex o [2004/09/21] threads/71966threads Mlnet Core Dumped : Fatal error '_pq_inse o [2004/11/21] threads/74180threads KSE problem. Applications those riched ma o [2005/01/20] threads/76513threads libpthread is not working o [2005/01/29] threads/76821threads Add access to gdb unique thread id o [2005/02/01] threads/76938threads include/unistd.h: ttyname_r prototype mis 12 problems total. From owner-freebsd-threads@FreeBSD.ORG Tue Mar 8 15:04:41 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7EDC16A4CE for ; Tue, 8 Mar 2005 15:04:41 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9307643D54 for ; Tue, 8 Mar 2005 15:04:41 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j28F4fXj007529 for ; Tue, 8 Mar 2005 07:04:41 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j28F4f1d007528 for freebsd-threads@freebsd.org; Tue, 8 Mar 2005 07:04:41 -0800 Date: Tue, 8 Mar 2005 07:04:41 -0800 From: Brooks Davis To: freebsd-threads@freebsd.org Message-ID: <20050308150441.GB31278@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tjCHc7DPkfUGtrlw" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Subject: pthread_t not defined by sys/types.h X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2005 15:04:42 -0000 --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It turns out that SUSv3: http://www.opengroup.org/onlinepubs/000095399/toc.htm states that following variables must be defined in sys/types.h (their definitions in pthread.h must be identical) pthread_attr_t pthread_barrier_t pthread_barrierattr_t pthread_cond_t pthread_condattr_t pthread_key_t pthread_mutex_t pthread_mutexattr_t pthread_once_t pthread_rwlock_t pthread_rwlockattr_t pthread_spinlock_t pthread_t It has been reported that Sun Grid Engine relies on this behavior. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --tjCHc7DPkfUGtrlw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCLb8EXY6L6fI4GtQRAiQQAKCSyRG5JMxVmlDYE/7P0fEN5msnMgCdF6Mq O/ignkOhH0qu1h9JTrMKDPU= =5ti+ -----END PGP SIGNATURE----- --tjCHc7DPkfUGtrlw-- From owner-freebsd-threads@FreeBSD.ORG Thu Mar 10 06:30:04 2005 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CDAB16A4CE for ; Thu, 10 Mar 2005 06:30:04 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3B3B43D73 for ; Thu, 10 Mar 2005 06:30:03 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2A6U36E097497 for ; Thu, 10 Mar 2005 06:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2A6U3p4097496; Thu, 10 Mar 2005 06:30:03 GMT (envelope-from gnats) Resent-Date: Thu, 10 Mar 2005 06:30:03 GMT Resent-Message-Id: <200503100630.j2A6U3p4097496@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-threads@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Thomas Lange Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B718816A4CE for ; Thu, 10 Mar 2005 06:22:29 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95B1B43D5A for ; Thu, 10 Mar 2005 06:22:29 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j2A6MTJj066261 for ; Thu, 10 Mar 2005 06:22:29 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id j2A6MTZn066260; Thu, 10 Mar 2005 06:22:29 GMT (envelope-from nobody) Message-Id: <200503100622.j2A6MTZn066260@www.freebsd.org> Date: Thu, 10 Mar 2005 06:22:29 GMT From: Thomas Lange To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: threads/78660: Java hangs unkillably in STOP state after fork() X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 06:30:04 -0000 >Number: 78660 >Category: threads >Synopsis: Java hangs unkillably in STOP state after fork() >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-threads >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Mar 10 06:30:03 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Thomas Lange >Release: 5.3 Release >Organization: >Environment: FreeBSD hellraiser.smega.com 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #2: Fri Feb 18 17:19:29 CET 2005 root@hellraiser.smega.com:/usr/obj/usr/src/sys/HELLRAISER-05-02-02 i386 >Description: After many calls of Runtime.getRuntime().exec(), which starts an external process, Java hangs reproducably in a STOP state and cannot be killed. (Not even with kill -9) >How-To-Repeat: Run any Java application, which makes extensive use of Runtime.getRuntime().exec(). With my application, I can reproduce the problem within an hour or so - on two different machines. >Fix: Apply David Xu's patch to kern_thread.c as described in http://lists.freebsd.org/pipermail/freebsd-current/2004-November/042407.html That change is also commited to 5.3-stable. However, maybe someone with a thorough understanding of the internal kernel structure should have a look at it. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-threads@FreeBSD.ORG Thu Mar 10 13:58:49 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0DAF16A4CE for ; Thu, 10 Mar 2005 13:58:49 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id A746043D31 for ; Thu, 10 Mar 2005 13:58:49 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id DB70F46B11; Thu, 10 Mar 2005 08:58:48 -0500 (EST) Date: Thu, 10 Mar 2005 13:56:28 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Antoine Brodin In-Reply-To: <20050226144511.25262941.antoine.brodin@laposte.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@FreeBSD.org Subject: Re: cvs commit: src/sys/kern uipc_sem.c X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 13:58:50 -0000 On Sat, 26 Feb 2005, Antoine Brodin wrote: > Robert Watson wrote: > > On Fri, 25 Feb 2005, Antoine Brodin wrote: > > > > > I think you forgot to increment i, maybe you should replace > > > sem_array[i] = ks; by sem_array[i++] = ks; ? And the " + 1" in the > > > KASSERT looks bogus too ;). > > > > Antoine, > > > > As usual, good eyes :-). I tested the loop code, and then proceeded > > to change other things, and neglected to run the test case afterwards. > > By the way, I'm not sure a race with other threads in the parent process > can happen during fork(): thread_single() is called at the beginning of > fork1() if the parent process has had threads and thread_single_end() is > called at the end. Perhaps a thread guru can confirm this. I've broadened the CC to include threads@ because I'm not entirely sure of the semantics of the single threading mechanism in kernel -- specifically, how it behaves in the presence of 1:1 threads. Just to provide a bit more context for those on the list -- uipc_sem.c does some paperwork at fork() time so the parent and child processes both have references to the same set of semaphores. The way this is done right now is that the thread in kernel calling fork takes a snapshot of the set of semaphores, bumping their reference counts, then goes off and adds them to the child which involves potentially sleeping memory allocation. Under the assumption that other threads in the parent might still be executing, I address the issue through the snapshot and then assign the references owned by the snapshop array to the child process as the memory allocation takes place. This adds some overhead, which would be nice to get rid of -- if the snapshot is unnecessary. So the question is -- will the parent process see any parallelism in kernel during fork() for any of our threading model, or do we prevent that? Robert N M Watson From owner-freebsd-threads@FreeBSD.ORG Thu Mar 10 14:11:06 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9731F16A4CE; Thu, 10 Mar 2005 14:11:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FE4943D46; Thu, 10 Mar 2005 14:11:06 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2AEB2YW049210; Thu, 10 Mar 2005 14:11:04 GMT (envelope-from davidxu@freebsd.org) Message-ID: <42305575.9000606@freebsd.org> Date: Thu, 10 Mar 2005 22:11:01 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050306 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: threads@freebsd.org cc: Antoine Brodin Subject: Re: cvs commit: src/sys/kern uipc_sem.c X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 14:11:06 -0000 Robert Watson wrote: >So the question is -- will the parent process see any parallelism in >kernel during fork() for any of our threading model, or do we prevent >that? > >Robert N M Watson > > > > When fork1() running, only the current forker thread can run, other threads in same process are just suspended by the forker, same as it it in exec(). I haven't looked uipc_sem.c, but as you said above, it seems sem can be shared between processes, you'd care if A and B are sharing same sem, but now B would like to fork a new child C, not sure if you will have the problem within this condition. David Xu From owner-freebsd-threads@FreeBSD.ORG Thu Mar 10 15:28:45 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FD4C16A4CE; Thu, 10 Mar 2005 15:28:45 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1B8B43D1D; Thu, 10 Mar 2005 15:28:44 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) j2AFSh9Q003192; Thu, 10 Mar 2005 10:28:43 -0500 (EST) Date: Thu, 10 Mar 2005 10:28:43 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Thomas Lange In-Reply-To: <200503100622.j2A6MTZn066260@www.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: freebsd-gnats-submit@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: threads/78660: Java hangs unkillably in STOP state after fork() X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 15:28:45 -0000 On Thu, 10 Mar 2005, Thomas Lange wrote: > >Organization: > >Environment: > FreeBSD hellraiser.smega.com 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #2: Fri Feb 18 17:19:29 CET 2005 root@hellraiser.smega.com:/usr/obj/usr/src/sys/HELLRAISER-05-02-02 i386 > > >Description: > After many calls of Runtime.getRuntime().exec(), which starts an external process, Java hangs reproducably in a STOP state and cannot be killed. (Not even with kill -9) > > >How-To-Repeat: > Run any Java application, which makes extensive use of Runtime.getRuntime().exec(). > With my application, I can reproduce the problem within an hour or so - on two different machines. > >Fix: > Apply David Xu's patch to kern_thread.c as described in > > http://lists.freebsd.org/pipermail/freebsd-current/2004-November/042407.html > > That change is also commited to 5.3-stable. Why is this a PR? It's fixed in both -stable and -current. -- DE From owner-freebsd-threads@FreeBSD.ORG Thu Mar 10 15:30:08 2005 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02DA616A4CE for ; Thu, 10 Mar 2005 15:30:08 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3E5E43D2F for ; Thu, 10 Mar 2005 15:30:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2AFU7xD058495 for ; Thu, 10 Mar 2005 15:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2AFU7lf058491; Thu, 10 Mar 2005 15:30:07 GMT (envelope-from gnats) Date: Thu, 10 Mar 2005 15:30:07 GMT Message-Id: <200503101530.j2AFU7lf058491@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Daniel Eischen Subject: Re: threads/78660: Java hangs unkillably in STOP state after fork() X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2005 15:30:08 -0000 The following reply was made to PR threads/78660; it has been noted by GNATS. From: Daniel Eischen To: Thomas Lange Cc: freebsd-gnats-submit@freebsd.org, Subject: Re: threads/78660: Java hangs unkillably in STOP state after fork() Date: Thu, 10 Mar 2005 10:28:43 -0500 (EST) On Thu, 10 Mar 2005, Thomas Lange wrote: > >Organization: > >Environment: > FreeBSD hellraiser.smega.com 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #2: Fri Feb 18 17:19:29 CET 2005 root@hellraiser.smega.com:/usr/obj/usr/src/sys/HELLRAISER-05-02-02 i386 > > >Description: > After many calls of Runtime.getRuntime().exec(), which starts an external process, Java hangs reproducably in a STOP state and cannot be killed. (Not even with kill -9) > > >How-To-Repeat: > Run any Java application, which makes extensive use of Runtime.getRuntime().exec(). > With my application, I can reproduce the problem within an hour or so - on two different machines. > >Fix: > Apply David Xu's patch to kern_thread.c as described in > > http://lists.freebsd.org/pipermail/freebsd-current/2004-November/042407.html > > That change is also commited to 5.3-stable. Why is this a PR? It's fixed in both -stable and -current. -- DE