From owner-freebsd-current@FreeBSD.ORG Thu Nov 29 18:14:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B42F16A418 for ; Thu, 29 Nov 2007 18:14:35 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (classis.ru [213.248.60.120]) by mx1.freebsd.org (Postfix) with ESMTP id 13E5413C458 for ; Thu, 29 Nov 2007 18:14:34 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from [81.19.90.199] (unknown [81.19.90.199]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: citrin@citrin.ru) by mail.classis.ru (Postfix) with ESMTP id 3784DB82D for ; Thu, 29 Nov 2007 20:52:34 +0300 (MSK) Message-ID: <474EFC5C.9060508@citrin.ru> Date: Thu, 29 Nov 2007 20:52:28 +0300 From: Anton Yuzhaninov User-Agent: Thunderbird by compcn MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Subject: 7.0-BETA3 - [thread taskq] eat 100% WCPU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 29 Nov 2007 18:14:35 -0000 1684 processes:26 running, 1639 sleeping, 19 waiting CPU states: 6.7% user, 0.0% nice, 54.5% system, 1.1% interrupt, 37.7% idle Mem: 1332M Active, 1903M Inact, 505M Wired, 118M Cache, 214M Buf, 76M Free Swap: 2060M Total, 2060M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 9 root 1 8 - 0K 16K CPU1 1 536:07 100.00% thread taskq 12 root 1 171 ki31 0K 16K RUN 0 53.5H 64.06% idle: cpu0 11 root 1 171 ki31 0K 16K RUN 1 50.3H 14.26% idle: cpu1 After 2 days of work thread taskq starts to eat all available CPU. In normal condition system work with about 80% idle. Kernel config - generic with removed inet6/sctp, raid controllers, fireware e.t.c. Processes which work with disk often sleep on filelist lock: $ find /usr/ -name not_exist load: 7.76 cmd: find 69836 [filelist lock] 0.00u 0.00s 0% 1044k load: 7.76 cmd: find 69836 [filelist lock] 0.00u 0.00s 0% 1044k load: 7.76 cmd: find 69836 [filelist lock] 0.00u 0.00s 0% 1044k On other servers I don't see this state. $ uname -srp FreeBSD 7.0-BETA3 amd64 Is it possible to debug this problem? -- WBR, Anton Yuzhaninov