From owner-freebsd-threads@FreeBSD.ORG Mon Sep 8 02:22:29 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 46C6D106569A for ; Mon, 8 Sep 2008 02:22:29 +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 345448FC1C for ; Mon, 8 Sep 2008 02:22:29 +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 m882MT81006844 for ; Mon, 8 Sep 2008 02:22:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m882MSnV006840 for freebsd-threads@FreeBSD.org; Mon, 8 Sep 2008 02:22:28 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Sep 2008 02:22:28 GMT Message-Id: <200809080222.m882MSnV006840@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, 08 Sep 2008 02:22:29 -0000 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/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 37 problems total. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. From owner-freebsd-threads@FreeBSD.ORG Mon Sep 8 22:51:11 2008 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76B7A106566B; Mon, 8 Sep 2008 22:51:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4FB958FC21; Mon, 8 Sep 2008 22:51:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m88MpBJb057125; Mon, 8 Sep 2008 22:51:11 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m88MpBOh057121; Mon, 8 Sep 2008 22:51:11 GMT (envelope-from linimon) Date: Mon, 8 Sep 2008 22:51:11 GMT Message-Id: <200809082251.m88MpBOh057121@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-threads@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: threads/127225: bug in lib/libthr/thread/thr_init.c 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, 08 Sep 2008 22:51:11 -0000 Synopsis: bug in lib/libthr/thread/thr_init.c Responsible-Changed-From-To: freebsd-bugs->freebsd-threads Responsible-Changed-By: linimon Responsible-Changed-When: Mon Sep 8 22:50:49 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=127225 From owner-freebsd-threads@FreeBSD.ORG Tue Sep 9 00:00:21 2008 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22F6A106567F for ; Tue, 9 Sep 2008 00:00:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1328E8FC19 for ; Tue, 9 Sep 2008 00:00:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8900Kbr062485 for ; Tue, 9 Sep 2008 00:00:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8900K6N062483; Tue, 9 Sep 2008 00:00:20 GMT (envelope-from gnats) Date: Tue, 9 Sep 2008 00:00:20 GMT Message-Id: <200809090000.m8900K6N062483@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: bin/127225: bug in lib/libthr/thread/thr_init.c X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2008 00:00:21 -0000 The following reply was made to PR threads/127225; it has been noted by GNATS. From: Kris Kennaway To: comperr Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/127225: bug in lib/libthr/thread/thr_init.c Date: Tue, 09 Sep 2008 09:28:21 +0930 comperr wrote: > FreeBSD starfx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #2: Sun Sep 7 21:15:11 EDT 2008 variable@starfx:/extra/backups/obj/src/sys/KERNKOOL i386 >> Description: > Firefox3, xchat, and others fail with: > Fatal error 'Cannot allocate red zone for initial thread' at line 384 in file /extra/src/lib/libthr/thread/thr_init.c (errno = 12) > .. (same error) ... > Fatal error 'Cannot allocate red zone for initial thread' at line 384 in file /extra/src/lib/libthr/thread/thr_init.c (errno = 12) > Bus error (core dumped) > >> How-To-Repeat: > run firefox3 >> Fix: > none at this time Usually means you're using an application that was linked to two versions of the same thread library (google the error message for extensive discussion). Usual cause is from an upgrade from an older version of FreeBSD that was not completed correctly. Kris From owner-freebsd-threads@FreeBSD.ORG Fri Sep 12 11:09:19 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 51E9A1065673 for ; Fri, 12 Sep 2008 11:09:19 +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 092828FC20 for ; Fri, 12 Sep 2008 11:09:18 +0000 (UTC) (envelope-from gofdt-freebsd-threads@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ke631-0005Vb-Lq for freebsd-threads@freebsd.org; Fri, 12 Sep 2008 10:38:43 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Sep 2008 10:38:43 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Sep 2008 10:38:43 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-threads@freebsd.org From: Ivan Voras Date: Fri, 12 Sep 2008 12:38:46 +0200 Lines: 38 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig66F62E32AD96AC284E21781C" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.16 (X11/20080724) X-Enigmail-Version: 0.95.0 Sender: news Subject: 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: Fri, 12 Sep 2008 11:09:19 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig66F62E32AD96AC284E21781C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I'm running apache2.2.9-worker without mod_php (with mod_fcgid and PHP as FastCGI) and a process or a thread repeatedly gets stuck: PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND= 5503 www 41 96 0 50820K 30960K umtxn 0 722:42 99.32% httpd It doesn't use sys time and ktrace doesn't record anything. Any clues where to dig next? I'm not using any unusual modules for apache, and the same configuration worked in 6.3 (this system was upgraded from 6.3 to 7.0-R - I checked that all apache dependancies are compiled for 7.0). --------------enig66F62E32AD96AC284E21781C 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIyka2ldnAQVacBcgRAi/pAKCi9no02sDPoEFAYEI9+n/RWX40XwCfazuB zfZittJNEn3v+h3JAeYnDLg= =/zsj -----END PGP SIGNATURE----- --------------enig66F62E32AD96AC284E21781C-- From owner-freebsd-threads@FreeBSD.ORG Fri Sep 12 17:15:55 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 5284D1065672 for ; Fri, 12 Sep 2008 17:15:55 +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 440438FC14 for ; Fri, 12 Sep 2008 17:15:55 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 0FBF31A3C38; Fri, 12 Sep 2008 09:58:09 -0700 (PDT) Date: Fri, 12 Sep 2008 09:58:09 -0700 From: Alfred Perlstein To: Ivan Voras Message-ID: <20080912165808.GE16977@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: 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: Fri, 12 Sep 2008 17:15:55 -0000 * Ivan Voras [080912 04:09] wrote: > Hi, > > I'm running apache2.2.9-worker without mod_php (with mod_fcgid and PHP > as FastCGI) and a process or a thread repeatedly gets stuck: > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 5503 www 41 96 0 50820K 30960K umtxn 0 722:42 99.32% httpd > > It doesn't use sys time and ktrace doesn't record anything. > > Any clues where to dig next? > > I'm not using any unusual modules for apache, and the same configuration > worked in 6.3 (this system was upgraded from 6.3 to 7.0-R - I checked > that all apache dependancies are compiled for 7.0). Try using "pstack" a few times. It's in ports. Also, gcore(1) might help. You can also try to attach using gdb. Basically, one of these tools should give you a stack trace which can help. It's interesting that the process is in "umtxn" though, is it multithreaded apache? Can you dump the threads? I think top(1) has an option to view each thread, how about trying that? thank you, -Alfred From owner-freebsd-threads@FreeBSD.ORG Fri Sep 12 22:16: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 E82D9106567C for ; Fri, 12 Sep 2008 22:16:38 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id B924A8FC0A for ; Fri, 12 Sep 2008 22:16:38 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1255910rvf.43 for ; Fri, 12 Sep 2008 15:16:38 -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=uz5Vbw+yj3c6OmKB1oHx34Oz7GN1kw1nTCskgseqOSU=; b=A3M0fW6ZeNZFfEbYH01A0Yu5Q/JBLxYWE30Y0+8nlAMfB5zYtY7Fr76SRKnp5an9fC 5+3VtrxXoMnq+MOHGrbz1CEgThrpXSAFANLREOzSNQeLY4hkku6gqGrTqo8FtPMdK12T ebrG68fI39Q0ryI8/rJlJcju+sWsztPxuTZdc= 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=GccV4QItdAw/AhkmhzPkJ2lsXm2Sd48paePPSZOLoJP2OK4wbCTDUsVxgpS9gAJACh 2CbNc0i8vAK2ZTTFO2G8iM++ulSpVMrLZm4kjGjOLaZYIKcbBhuWyqdMrGUyaBgEPQiI DaOE0HwHAkiJkPM+8ucbQtMtA4jxnJwUWo544= Received: by 10.141.137.6 with SMTP id p6mr2905146rvn.279.1221255891221; Fri, 12 Sep 2008 14:44:51 -0700 (PDT) Received: by 10.141.153.13 with HTTP; Fri, 12 Sep 2008 14:44:51 -0700 (PDT) Message-ID: <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> Date: Fri, 12 Sep 2008 23:44:51 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Alfred Perlstein" In-Reply-To: <20080912165808.GE16977@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> X-Google-Sender-Auth: 9219905d203f2681 Cc: 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: Fri, 12 Sep 2008 22:16:39 -0000 2008/9/12 Alfred Perlstein : > Try using "pstack" a few times. It's in ports. > > Also, gcore(1) might help. Will try. > You can also try to attach using gdb. I did, but either I'm missing something or I'm not using it well, because I can't get a backtrace. How do I select threads to backtrace? How do I pick what thread to backtrace? > Basically, one of these tools should give you a stack trace which > can help. > > It's interesting that the process is in "umtxn" though, is it > multithreaded apache? Can you dump the threads? I think top(1) > has an option to view each thread, how about trying that? Yes, it's multithreaded apache. This did help somewhat - when I do it 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. From owner-freebsd-threads@FreeBSD.ORG Fri Sep 12 22:52:52 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 2004B106566C; Fri, 12 Sep 2008 22:52:52 +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 0D5A18FC0A; Fri, 12 Sep 2008 22:52:52 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 027761A3C37; Fri, 12 Sep 2008 15:52:52 -0700 (PDT) Date: Fri, 12 Sep 2008 15:52:51 -0700 From: Alfred Perlstein To: Ivan Voras Message-ID: <20080912225251.GG16977@elvis.mu.org> References: <20080912165808.GE16977@elvis.mu.org> <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9bbcef730809121444u34991c52m2cbc01a8ada47eb5@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: 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: Fri, 12 Sep 2008 22:52:52 -0000 * Ivan Voras [080912 14:45] wrote: > 2008/9/12 Alfred Perlstein : > > > Try using "pstack" a few times. It's in ports. > > > > Also, gcore(1) might help. > > Will try. > > > You can also try to attach using gdb. > > I did, but either I'm missing something or I'm not using it well, > because I can't get a backtrace. How do I select threads to backtrace? > How do I pick what thread to backtrace? i think the command is 'info threads' or 'show threads' then i think you just type 'thread FOO' to select the thread. > > > Basically, one of these tools should give you a stack trace which > > can help. > > > > It's interesting that the process is in "umtxn" though, is it > > multithreaded apache? Can you dump the threads? I think top(1) > > has an option to view each thread, how about trying that? > > Yes, it's multithreaded apache. This did help somewhat - when I do it > 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. yeah its stuck in userspace doing something.. -- - Alfred Perlstein