From owner-freebsd-questions@FreeBSD.ORG Sat Oct 9 18:45:09 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 28D79106564A for ; Sat, 9 Oct 2010 18:45:09 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id B33628FC08 for ; Sat, 9 Oct 2010 18:45:08 +0000 (UTC) Received: by ewy27 with SMTP id 27so1139264ewy.13 for ; Sat, 09 Oct 2010 11:45:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to:date :message-id:subject:from:to:cc:content-type; bh=ljDKtsSX0AUsAv73HiSLMqn7nbxUkTpRXEencf6Fas4=; b=MnoxxxRjmmpDmqU18oLwJYKfMeWeBY3YlZiHTsR6hjMNbx90SrmpPuom+wvcpXCoHF EkHWObZt19281aKHGTEDf8BtyNSnIKfqYI0bjwtHzGEhGyz9EGP8Xi0zMbbl2Q7s+VB0 Ri/vsD4mJ+Ht23LX/zHU8u0OnMlwR7RUBOcjQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; b=R8OcUQNET1V4FP2CBYhnJvKWXwx+FIA5uAZKMO3JemzdS1XJVrVVMdJraiCC2h9yHx GSbpUSBmYzq+Qm97sX+kw8IMxsbi2GRqrWjAkiUgwXHrsmN+KPII90sDuCP7wxMgcd7f sHNYlfvO0FMHtIpClKfqyXlFF9HbRmNAWPhkY= MIME-Version: 1.0 Received: by 10.213.11.17 with SMTP id r17mr2405313ebr.66.1286649907410; Sat, 09 Oct 2010 11:45:07 -0700 (PDT) Received: by 10.14.47.14 with HTTP; Sat, 9 Oct 2010 11:45:07 -0700 (PDT) Date: Sat, 9 Oct 2010 18:45:07 +0000 Message-ID: From: "b. f." To: kes-kes@yandex.ru Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@FreeBSD.org Subject: Re: 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: bf1783@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Oct 2010 18:45:09 -0000 > How to obtain what nasty happen, which process take 36-50% of CPU > resource? It partly depends upon the version of the OS that you are running, your hardware, and your configuration. 2008 interrupts/sec is high, but not improbably so, for kern.hz>=1000, and not beyond the capabilities of today's average computer, although it may not be optimal for your workloads. So it may not actually be a problem with too many interrupts, but rather with some erroneous system accounting. This can happen, for example, if your computer is using some of the deeper power-saving C-states, but using them poorly, as for example in: http://lists.freebsd.org/pipermail/freebsd-current/2010-August/019383.html So you may want to examine, and perhaps adjust, your choice of kernel timers, kern.hz, and power-saving settings. Device polling can also be a factor, if you are using it. b.