From owner-freebsd-questions@FreeBSD.ORG Sun Oct 10 05:56:02 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 1C2DD1065672 for ; Sun, 10 Oct 2010 05:56:02 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 6B4138FC12 for ; Sun, 10 Oct 2010 05:56:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o9A5twcI045472; Sun, 10 Oct 2010 16:55:59 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 10 Oct 2010 16:55:58 +1100 (EST) From: Ian Smith To: kes-kes@yandex.ru In-Reply-To: <20101009204915.0360410656F1@hub.freebsd.org> Message-ID: <20101010161330.R2036@sola.nimnet.asn.au> References: <20101009204915.0360410656F1@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Oct 2010 05:56:02 -0000 In freebsd-questions Digest, Vol 331, Issue 13, Message: 8 On Sat, 9 Oct 2010 20:05:48 +0300 ??????? ??????? wrote: > Content-Type: text/plain; charset=windows-1251 ^^^^^^^^^^^^ Hi KES, long time .. > #systat -v > 1 users Load 0.74 0.71 0.55 Oct 9 19:53 [..] > Proc: Interrupts > r p d s w Csw Trp Sys Int Sof Flt 24 cow 2008 total > 2 3 39 23k 67 563 9 1710 47 15 zfod 9 ata0 irq14 > ozfod nfe0 irq23 > 23.1%Sys 50.8%Intr 1.3%User 0.0%Nice 24.8%Idle %ozfod 1999 cpu0: time > | | | | | | | | | | | daefr > ============+++++++++++++++++++++++++> 6 prcfr Yes, system and esp. interrupt time is heavy .. 23k context switches!? In addition to b. f.'s good advice .. as you later said, 2000 Hz slicing _should_ be ok, unless a slow CPU? Or perhaps a fast CPU throttled back too far .. powerd? Check sysctl dev.cpu.0.freq while this is happening. Disable p4tcc if it's a modern CPU; that usually hurts more than helps. Disable polling if you're using that .. you haven't provided much info, like is this with any network load, despite nfe0 showing no interrupts? > #top > last pid: 24571; load averages: 0.10, 0.49, 0.50 up 0+19:15:01 19:56:36 > 42 processes: 3 running, 39 sleeping > CPU: 0.7% user, 0.0% nice, 21.0% system, 36.3% interrupt, 41.9% idle > Mem: 305M Active, 767M Inact, 252M Wired, 468K Cache, 213M Buf, 650M Free > Swap: 4063M Total, 4063M Free > > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND > 1054 bind 4 4 0 134M 109M kqread 0:51 0.00% named > 986 root 1 44 0 5692K 1408K RUN 0:50 0.00% syslogd > 1162 clamav 1 4 0 4616K 1468K accept 0:46 0.00% smtp-gated > 11731 clamav 1 20 0 27948K 9728K pause 0:03 0.00% freshclam > 11791 root 1 -58 0 7848K 4120K bpf 0:02 0.00% arpwatch > 13208 root 1 44 0 10700K 4144K select 0:01 0.00% sendmail > 13298 root 1 8 0 6748K 1440K nanslp 0:00 0.00% cron > 12802 root 1 44 0 22880K 4004K select 0:00 0.00% sshd > > > How to obtain what nasty happen, which process take 36-50% of CPU > resource? Try 'top -S'. It's almost certainly system process[es], not shown above. cheers, Ian