From owner-freebsd-current@FreeBSD.ORG Thu Nov 4 22:28:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 833FC16A4CE for ; Thu, 4 Nov 2004 22:28:41 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 341AD43D5D for ; Thu, 4 Nov 2004 22:28:41 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iA4MSVcQ072195; Thu, 4 Nov 2004 16:28:31 -0600 (CST) (envelope-from dan) Date: Thu, 4 Nov 2004 16:28:31 -0600 From: Dan Nelson To: Marc Ramirez Message-ID: <20041104222831.GD10428@dan.emsphone.com> References: <200411032312.50664.marc.ramirez@bluecirclesoft.com> <20041104143644.GA36101@rogue.acs.lan> <200411041634.39570.marc.ramirez@bluecirclesoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411041634.39570.marc.ramirez@bluecirclesoft.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Mike Makonnen Subject: Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 22:28:41 -0000 In the last episode (Nov 04), Marc Ramirez said: > On Thursday 04 November 2004 09:36 am, Mike Makonnen wrote: > > Hmm, looks like the application is using libthr and not libpthread. > > I'll take a look at it, but in the mean time you might want to map > > libthr and libc_r to libpthread in libmap.conf(5). > > > > Can all other users with this problem verify which threading > > library they're running? You can use the following command on the > > binary. For example: # ldd /path/to/binary > > Not me. Thanks! I just noticed this on my machine as well (SMP, 5.3-stable as of yesterday), running a testsuite program linked to libpthreads. It creates 10 threads whose only job is to fork(), exec /bin/sleep, kill -9 the child, and wait for the status. Each thread does this 1000 times in a tight loop. Occasionally the whole thing will end up STOPped, but resumes within 60 seconds. If I ktrace the process during this, I see a long delay followed by: 39117 pike RET fork 0 32592 pike RET fork 39117/0x98cd Could there be a race or deadlock within the kernel's fork() routines? What happens if two threads on different CPUs decide to fork at the same time? -- Dan Nelson dnelson@allantgroup.com