From owner-freebsd-threads@FreeBSD.ORG Sun Sep 14 11:20:07 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 D6B691065675 for ; Sun, 14 Sep 2008 11:20:07 +0000 (UTC) (envelope-from gofdt-freebsd-threads@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9ADC68FC1C for ; Sun, 14 Sep 2008 11:20:07 +0000 (UTC) (envelope-from gofdt-freebsd-threads@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Kepe6-0003eC-IQ for freebsd-threads@freebsd.org; Sun, 14 Sep 2008 11:20:02 +0000 Received: from 89-172-50-143.adsl.net.t-com.hr ([89.172.50.143]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Sep 2008 11:20:02 +0000 Received: from ivoras by 89-172-50-143.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 14 Sep 2008 11:20:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-threads@freebsd.org From: Ivan Voras Date: Sun, 14 Sep 2008 13:16:25 +0200 Lines: 30 Message-ID: References: <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> <20080912225251.GG16977@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA7E471AA4EA83D46C4A94836" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-50-143.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) In-Reply-To: <20080912225251.GG16977@elvis.mu.org> X-Enigmail-Version: 0.95.7 Sender: news Subject: Re: Apache-worker stuck at 100% CPU 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: Sun, 14 Sep 2008 11:20:08 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA7E471AA4EA83D46C4A94836 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Alfred Perlstein wrote: > yeah its stuck in userspace doing something.. Update: upgrading to 7-STABLE apparently fixed it - it's been two days and it's stable. I'm worried because I didn't find out why was it misbehaving in the first place. --------------enigA7E471AA4EA83D46C4A94836 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjM8okACgkQldnAQVacBcg+9gCfYyypzNyVt5B9LlfLaRZs05ae 6L8An1CrtCXjAk1bipY8yAeVtuggRomu =yxPG -----END PGP SIGNATURE----- --------------enigA7E471AA4EA83D46C4A94836-- From owner-freebsd-threads@FreeBSD.ORG Mon Sep 15 15:18:57 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 551D41065688 for ; Mon, 15 Sep 2008 15:18:57 +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 441418FC21 for ; Mon, 15 Sep 2008 15:18:57 +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 m8FFIvMR019058 for ; Mon, 15 Sep 2008 15:18:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8FFIuGX019054 for freebsd-threads@FreeBSD.org; Mon, 15 Sep 2008 15:18:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Sep 2008 15:18:56 GMT Message-Id: <200809151518.m8FFIuGX019054@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, 15 Sep 2008 15:18:57 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o threa/127225 threads bug in lib/libthr/thread/thr_init.c o threa/126950 threads [patch] rtld(1): rtld malloc is thread-unsafe o kern/126128 threads [patch] pthread_condattr_getpshared is broken o threa/122923 threads 'nice' does not prevent background process from steali o threa/121336 threads lang/neko threading ok on UP, broken on SMP (FreeBSD 7 o threa/118715 threads kse problem o threa/116668 threads can no longer use jdk15 with libthr on -stable SMP o threa/116181 threads /dev/io-related io access permissions are not propagat o threa/115211 threads pthread_atfork misbehaves in initial thread o threa/110636 threads [request] gdb(1): using gdb with multi thread applicat o threa/110306 threads apache 2.0 segmentation violation when calling gethost o threa/103975 threads Implicit loading/unloading of libpthread.so may crash o threa/101323 threads fork(2) in threaded programs broken. s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc s threa/84483 threads problems with devel/nspr and -lc_r on 4.x o threa/83914 threads [libc] popen() doesn't work in static threaded program o threa/80992 threads abort() sometimes not caught by gdb depending on threa o threa/80435 threads panic on high loads o threa/79887 threads [patch] freopen() isn't thread-safe o threa/79683 threads svctcp_create() fails if multiple threads call at the s threa/76694 threads fork cause hang in dup()/close() function in child (-l s threa/76690 threads fork hang in child for -lc_r o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag o threa/75273 threads FBSD 5.3 libpthread (KSE) bug o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST o threa/70975 threads [sysvipc] unexpected and unreliable behaviour when usi s threa/69020 threads pthreads library leaks _gc_mutex s threa/49087 threads Signals lost in programs linked with libc_r s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under s threa/40671 threads pthread_cancel doesn't remove thread from condition qu s threa/39922 threads [threads] [patch] Threaded applications executed with s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra s threa/34536 threads accept() blocks other threads s bin/32295 threads pthread(3) dont dequeue signals s threa/30464 threads pthread mutex attributes -- pshared s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o 38 problems total. From owner-freebsd-threads@FreeBSD.ORG Mon Sep 15 23:04:48 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 90B701065673 for ; Mon, 15 Sep 2008 23:04:48 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mx1.freebsd.org (Postfix) with ESMTP id 607798FC15 for ; Mon, 15 Sep 2008 23:04:48 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3100623rvf.43 for ; Mon, 15 Sep 2008 16:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=48+9+53/B2AbTkYzUuigFyqLbcmavBAX7oK2COwabKI=; b=KITMRcDbJa8UHMVeHsN0BkaUEJyniuJHwnJXmv/pjdmxzEL5ppAb52r2fwGNLtq4Bn 9vIyMnVyQRwlnhTZQQDBfldHm/xk7AmADlMkJnplqLdFnjkoh4KLkXKDiGqkmtUgAXV8 PcZEPKN5TrOyg0vVY3Zu651q6kX4yEw9MHpDI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=neCyzrbNUZqIsSIjYVlsFob6nKZp1wyvGbWxC/Dygh34k02meXjFCt3zjeiDJN3pGc if0dIjFWbFKvyqEZziuLio8rsJd0XjlGZIacXKIatBFVWSfn3wytvhJzVQPpykV8ex8k W9kuImHYQQzbergZqTdBOUlkdbtxe6h+im4zw= Received: by 10.141.106.14 with SMTP id i14mr5179726rvm.152.1221519887962; Mon, 15 Sep 2008 16:04:47 -0700 (PDT) Received: by 10.141.159.2 with HTTP; Mon, 15 Sep 2008 16:04:47 -0700 (PDT) Message-ID: <9bbcef730809151604i28533745m286e7314810d0362@mail.gmail.com> Date: Tue, 16 Sep 2008 01:04:47 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Alfred Perlstein" In-Reply-To: <20080912225251.GG16977@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> <20080912225251.GG16977@elvis.mu.org> X-Google-Sender-Auth: 3701b5f21a5bba0d Cc: stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Apache-worker stuck at 100% CPU 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, 15 Sep 2008 23:04:48 -0000 2008/9/13 Alfred Perlstein : >> Yes, it's multithreaded apache. This did help somewhat - when I show threads in top >> I see that it's not actually stuck in umtxn - there's one thread that >> consumes the CPU and it's apparently always running (in state CPUx). >> >> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND >> 7212 www 103 0 30340K 7932K CPU2 2 444:23 99.02% httpd >> >> I'm currently upgrading the system to 7-STABLE, to see if it helps. It didn't help. Exactly the same symptom happened again. It looks like it happens a few days after the last system reboot. After it happens the first time, restarting Apache immediately produces one such "stuck" thread - it looks like some system state gets corrupted over time. >> How do I pick what thread to backtrace in gdb? > > i think the command is 'info threads' or 'show > threads' then i think you just type > 'thread FOO' to select the thread. Both commands don't work / don't exist. Any others? (background: apache22-worker port, no mod_php, on 7.0 and 7-STABLE suddenly gets stuck at 100% CPU; the same setup worked on 6-STABLE. I'm looking for ideas) From owner-freebsd-threads@FreeBSD.ORG Tue Sep 16 02:27:38 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 8CB981065680; Tue, 16 Sep 2008 02:27:38 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 74C328FC1E; Tue, 16 Sep 2008 02:27:38 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 27ECC1A3C38; Mon, 15 Sep 2008 19:27:38 -0700 (PDT) Date: Mon, 15 Sep 2008 19:27:38 -0700 From: Alfred Perlstein To: Ivan Voras Message-ID: <20080916022738.GJ36572@elvis.mu.org> References: <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> <20080912225251.GG16977@elvis.mu.org> <9bbcef730809151604i28533745m286e7314810d0362@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9bbcef730809151604i28533745m286e7314810d0362@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Apache-worker stuck at 100% CPU 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: Tue, 16 Sep 2008 02:27:38 -0000 * Ivan Voras [080915 16:05] wrote: > 2008/9/13 Alfred Perlstein : > > >> Yes, it's multithreaded apache. This did help somewhat - when I show threads in top > >> I see that it's not actually stuck in umtxn - there's one thread that > >> consumes the CPU and it's apparently always running (in state CPUx). > >> > >> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND > >> 7212 www 103 0 30340K 7932K CPU2 2 444:23 99.02% httpd > >> > >> I'm currently upgrading the system to 7-STABLE, to see if it helps. > > It didn't help. Exactly the same symptom happened again. It looks like > it happens a few days after the last system reboot. After it happens > the first time, restarting Apache immediately produces one such > "stuck" thread - it looks like some system state gets corrupted over > time. > > >> How do I pick what thread to backtrace in gdb? > > > > i think the command is 'info threads' or 'show > > threads' then i think you just type > > 'thread FOO' to select the thread. > > Both commands don't work / don't exist. Any others? > > (background: apache22-worker port, no mod_php, on 7.0 and 7-STABLE > suddenly gets stuck at 100% CPU; the same setup worked on 6-STABLE. > I'm looking for ideas) I'm sorry, I really can't help at this point other than to look through the documents myself to figure out how to do a backtrace/select threads. Give it a shot, and let us know and we can go further. Apologies, -Alfred From owner-freebsd-threads@FreeBSD.ORG Tue Sep 16 09:12:02 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 5461D10656B7 for ; Tue, 16 Sep 2008 09:12:02 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 23D7B8FC37 for ; Tue, 16 Sep 2008 09:12:01 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3395271rvf.43 for ; Tue, 16 Sep 2008 02:12:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=zyOipxLHinL8bH0ZT8bZ3EQlmZRkqdDuDsbT6tjzRSU=; b=hdkNIIYCwKa6i33KQjzT8fu4reD/qmT31FikuJ56Kk+tUIGxx36rH5SeV7VGkkgXQ7 lR2DazTAjZx4pO9bhPnNqpwNRwvxWDVb9+nXThrYx6UysJdJAybzHgaIZt5/l35Q2/iQ FgvzOUHWl++b1QbQsrB9GYiGLCR8qJOTm9G4g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=t4uUbly1i5CL7XzGvVAiN4AszPa/3V4l6BoxT5QAElThmCq+XXRJXbRJhwyfLL0ftB aq5l/pQ4qFYlhH1QDMF2z3NcWlPk+fdvUhfk04FtH3m9K9hwgETRc38HQMMxPgtsFKWC 6Y75xyADdP6+BAMzexQwVX/BJoJkoed1Bd2zg= Received: by 10.141.28.4 with SMTP id f4mr5490618rvj.66.1221556321244; Tue, 16 Sep 2008 02:12:01 -0700 (PDT) Received: by 10.141.159.2 with HTTP; Tue, 16 Sep 2008 02:12:01 -0700 (PDT) Message-ID: <9bbcef730809160212m72fffc7k93d0c92ace2b7c19@mail.gmail.com> Date: Tue, 16 Sep 2008 11:12:01 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Alfred Perlstein" In-Reply-To: <20080916022738.GJ36572@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> <20080912225251.GG16977@elvis.mu.org> <9bbcef730809151604i28533745m286e7314810d0362@mail.gmail.com> <20080916022738.GJ36572@elvis.mu.org> X-Google-Sender-Auth: 73c0ddf0d882732d Cc: stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Apache-worker stuck at 100% CPU 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: Tue, 16 Sep 2008 09:12:02 -0000 2008/9/16 Alfred Perlstein : > * Ivan Voras [080915 16:05] wrote: >> >> How do I pick what thread to backtrace in gdb? >> > >> > i think the command is 'info threads' or 'show >> > threads' then i think you just type >> > 'thread FOO' to select the thread. >> >> Both commands don't work / don't exist. Any others? >> >> (background: apache22-worker port, no mod_php, on 7.0 and 7-STABLE >> suddenly gets stuck at 100% CPU; the same setup worked on 6-STABLE. >> I'm looking for ideas) > > I'm sorry, I really can't help at this point other than to look > through the documents myself to figure out how to do a backtrace/select > threads. > > Give it a shot, and let us know and we can go further. Sorry, I should have been more verbose - "info threads" should work but it doesn't - I can attach and get threads from a "regular" multithreaded process, but when yesterday when I attached to the stuck process, I couldn't get the list of threads. I'll try again the next time it gets stuck and try to provide more information. From owner-freebsd-threads@FreeBSD.ORG Tue Sep 16 16:42:03 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 A2F6D106567C; Tue, 16 Sep 2008 16:42:03 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 8F8A98FC18; Tue, 16 Sep 2008 16:42:03 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 475371A3C36; Tue, 16 Sep 2008 09:42:03 -0700 (PDT) Date: Tue, 16 Sep 2008 09:42:03 -0700 From: Alfred Perlstein To: Ivan Voras Message-ID: <20080916164203.GL36572@elvis.mu.org> References: <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> <20080912225251.GG16977@elvis.mu.org> <9bbcef730809151604i28533745m286e7314810d0362@mail.gmail.com> <20080916022738.GJ36572@elvis.mu.org> <9bbcef730809160212m72fffc7k93d0c92ace2b7c19@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9bbcef730809160212m72fffc7k93d0c92ace2b7c19@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Apache-worker stuck at 100% CPU 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: Tue, 16 Sep 2008 16:42:03 -0000 * Ivan Voras [080916 02:12] wrote: > 2008/9/16 Alfred Perlstein : > > * Ivan Voras [080915 16:05] wrote: > > >> >> How do I pick what thread to backtrace in gdb? > >> > > >> > i think the command is 'info threads' or 'show > >> > threads' then i think you just type > >> > 'thread FOO' to select the thread. > >> > >> Both commands don't work / don't exist. Any others? > >> > >> (background: apache22-worker port, no mod_php, on 7.0 and 7-STABLE > >> suddenly gets stuck at 100% CPU; the same setup worked on 6-STABLE. > >> I'm looking for ideas) > > > > I'm sorry, I really can't help at this point other than to look > > through the documents myself to figure out how to do a backtrace/select > > threads. > > > > Give it a shot, and let us know and we can go further. > > Sorry, I should have been more verbose - "info threads" should work > but it doesn't - I can attach and get threads from a "regular" > multithreaded process, but when yesterday when I attached to the stuck > process, I couldn't get the list of threads. I'll try again the next > time it gets stuck and try to provide more information. If it happens again, you could try sending it a SIGABRT or SEGV and then trying to diagnose the core dump. Or try using gcore to generate a coredump and debug that. -- - Alfred Perlstein From owner-freebsd-threads@FreeBSD.ORG Tue Sep 16 16:45:17 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 F22DF1065677 for ; Tue, 16 Sep 2008 16:45:17 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id C20638FC1B for ; Tue, 16 Sep 2008 16:45:17 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1775362wah.3 for ; Tue, 16 Sep 2008 09:45:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=aYkv+8BwB3qrWqfAZ2LkggfzjHGl7BoFYvpmdGngMd8=; b=BGJDyUw30035BlxGs6YIEd1uXM3p7NLVc3wo3i1OnA0bLWsLYs+5JO5Kt10oGqpV2m ik/no5DD9tNHgFQU7XrqzcUZSHHc2vT8Ap7ZhEeNPHGzzEG4sd0Xaso2kIn4LBq40NEO FrIl1C0F0cydRYt3+MOs40eGASb+aQupWMLIA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=swdAAZ2kxEZr6S9kDNbJ+McCkP2BMlkScVvocTkubm9NcccpbkSU+4e1VxJzsGTd8x RTfEVPSePGnrPK8koK1eNSRhBBfB8vxFQ83pCG6CTGM8sUaVsv9lHOLKamiAZHzYKpFH 18Z46gH1TA3GKlH7gRxqfTLN35RNBBXpTDcHg= Received: by 10.141.164.13 with SMTP id r13mr5831901rvo.150.1221583517325; Tue, 16 Sep 2008 09:45:17 -0700 (PDT) Received: by 10.141.159.2 with HTTP; Tue, 16 Sep 2008 09:45:17 -0700 (PDT) Message-ID: <9bbcef730809160945y8f472bfw60af0d22149d9376@mail.gmail.com> Date: Tue, 16 Sep 2008 18:45:17 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Alfred Perlstein" In-Reply-To: <20080916164203.GL36572@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> <20080912225251.GG16977@elvis.mu.org> <9bbcef730809151604i28533745m286e7314810d0362@mail.gmail.com> <20080916022738.GJ36572@elvis.mu.org> <9bbcef730809160212m72fffc7k93d0c92ace2b7c19@mail.gmail.com> <20080916164203.GL36572@elvis.mu.org> X-Google-Sender-Auth: f22fd81409ab0b66 Cc: stable@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Apache-worker stuck at 100% CPU 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: Tue, 16 Sep 2008 16:45:18 -0000 2008/9/16 Alfred Perlstein : > * Ivan Voras [080916 02:12] wrote: >> Sorry, I should have been more verbose - "info threads" should work >> but it doesn't - I can attach and get threads from a "regular" >> multithreaded process, but when yesterday when I attached to the stuck >> process, I couldn't get the list of threads. I'll try again the next >> time it gets stuck and try to provide more information. > > If it happens again, you could try sending it a SIGABRT or SEGV > and then trying to diagnose the core dump. > > Or try using gcore to generate a coredump and debug that. It happens approximately every two days; I've rebuild apache with debugging symbols so it will be easier to dig around this time.