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)