From owner-freebsd-questions@FreeBSD.ORG Sat Oct 9 20:42:42 2010 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 566CE106564A for ; Sat, 9 Oct 2010 20:42:42 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forward20.mail.yandex.net (forward20.mail.yandex.net [95.108.253.145]) by mx1.freebsd.org (Postfix) with ESMTP id 011538FC16 for ; Sat, 9 Oct 2010 20:42:41 +0000 (UTC) Received: from smtp16.mail.yandex.net (smtp16.mail.yandex.net [95.108.252.16]) by forward20.mail.yandex.net (Yandex) with ESMTP id 2C68E5D10FBF; Sun, 10 Oct 2010 00:42:40 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1286656960; bh=jkvlAk1/5av8n1rBbqPPUjMoDMNukRevtJPhS0sqQUs=; h=Date:From:Reply-To:Message-ID:To:CC:Subject:In-Reply-To: References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=BA9h1BjcBVBSkw5zl3N2OG4jpVx//I+CqAGZSR4LGuvjLT5xylA98ZEOEH7cIyGhO YMZ5EPgvsRRTMgNxZdZa4BlPbGwvkqUuKVgtvjDRYuitS9kkB/fAV7y+WBM6/nD5Wk po8Z9tEu34SPvUixs5EI2SPalADLf43bowwSZEMU= Received: from HOMEUSER (mail.freeline.in.ua [77.93.36.201]) by smtp16.mail.yandex.net (Yandex) with ESMTPA id 7E67716000A7; Sun, 10 Oct 2010 00:42:39 +0400 (MSD) X-Nat-Received: from [192.168.11.5]:1636 [ident-empty] by SPAM FILTER: with TPROXY id 1286657045.11880 abuse-to kes-kes@yandex.ru Date: Sat, 9 Oct 2010 23:42:42 +0300 From: =?utf-8?B?0JrQvtC90YzQutC+0LIg0JXQstCz0LXQvdC40Lk=?= X-Mailer: The Bat! (v4.0.24) Professional Organization: =?utf-8?B?0KfQnyDQmtC+0L3RjNC60L7QsiwgRnJlZUxpbmU=?= X-Priority: 3 (Normal) Message-ID: <1673286593.20101009234242@yandex.ru> To: "b. f." In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit X-Yandex-TimeMark: 1286656960 X-Yandex-Spam: 1 X-Yandex-Front: smtp16.mail.yandex.net Cc: bf1783@gmail.com, freebsd-questions@FreeBSD.org Subject: Re[2]: How to obtain which interrupts cause system to hang? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?utf-8?B?0JrQvtC90YzQutC+0LIg0JXQstCz0LXQvdC40Lk=?= List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Oct 2010 20:42:42 -0000 Здравствуйте, b.. Вы писали 9 октября 2010 г., 21:45:07: >> How to obtain what nasty happen, which process take 36-50% of CPU >> resource? bf> It partly depends upon the version of the OS that you are running, bf> your hardware, and your configuration. 2008 interrupts/sec is high, bf> but not improbably so, for kern.hz>=1000, and not beyond the bf> capabilities of today's average computer, although it may not be bf> optimal for your workloads. So it may not actually be a problem with bf> too many interrupts, but rather with some erroneous system accounting. bf> This can happen, for example, if your computer is using some of the bf> deeper power-saving C-states, but using them poorly, as for example bf> in: bf> http://lists.freebsd.org/pipermail/freebsd-current/2010-August/019383.html bf> So you may want to examine, and perhaps adjust, your choice of kernel bf> timers, kern.hz, and power-saving settings. Device polling can also bf> be a factor, if you are using it. system is one processor vpn_shadow# uname -a FreeBSD vpn_shadow.in 7.3-RELEASE-p2 FreeBSD 7.3-RELEASE-p2 #3: Mon Jul 26 01:56:03 EEST 2010 kes@in:/usr/obj/usr/src/sys/vpn amd64 kern.hz is 2000, Interrupts 1984 total is ok polling is enabled. Server runs about 6month and... and now it has interrupts: 13.5% system, 47.7% interrupt I can not imaginge what happen, in /var/log/* is silent... all is ok as usual. Network while that is happening is unstable. ping on 100Mbit link is 60ms. -- С уважением, Коньков mailto:kes-kes@yandex.ru