From owner-freebsd-questions@FreeBSD.ORG Mon Oct 11 08:43:04 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 BFDD4106566B for ; Mon, 11 Oct 2010 08:43:04 +0000 (UTC) (envelope-from four.harrisons@googlemail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 471BC8FC15 for ; Mon, 11 Oct 2010 08:43:03 +0000 (UTC) Received: by bwz16 with SMTP id 16so575499bwz.13 for ; Mon, 11 Oct 2010 01:43:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:subject:from:to:cc :date:mime-version:content-type:content-transfer-encoding; bh=6J76WLCp72Xe6EmT9o4+JAqgWZkEZvD83D98pRsPkDE=; b=xdxe70HhKMBorNkkQO1GcdS2+TFBTdEM+CfoSHZo4JjEXqJlkJ5WgvJXlEA0iRxos2 9DB9mnf6KPg9Jr3ja2lBMF2LJYzwmwFCd4NURxURFBdk1tHQSm19IS8LhZIkuWLSvlFA aX8sglu/o88DAqUeqPywZdQA9pf08hl4n2zcI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:subject:from:to:cc:date:mime-version:content-type :content-transfer-encoding; b=NDdddFiV1M4EnW9K9EVCW0/MvqTnDDW5hOYHIRq63xaCpveTHrYUVxFVHSzASdg6Ie mNGXaTUYGszvEWCKhcwClpPOb4y3HOxVoRx0Jc68++qKgfBzHq01y90jVkhB+zAYEL7k mK+0oCzVvgfkOVEN686f03orNlRqtLMWa1+0Y= Received: by 10.204.126.5 with SMTP id a5mr400039bks.177.1286786582461; Mon, 11 Oct 2010 01:43:02 -0700 (PDT) Received: from ecs ([213.8.162.222]) by mx.google.com with ESMTPS id g8sm555673bkg.11.2010.10.11.01.42.59 (version=SSLv3 cipher=RC4-MD5); Mon, 11 Oct 2010 01:43:01 -0700 (PDT) Message-ID: <4cb2ce15.4808cc0a.019a.13fb@mx.google.com> From: four.harrisons@googlemail.com To: kes-kes@yandex.ru Date: Sun, 10 Oct 2010 10:40:14 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: 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 List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2010 08:43:04 -0000 On Sun, 10 Oct 2010, ??????? ??????? wrote:=0D=0A > >> #systat -v=0D=0A = > >> 1 users Load 0.74 0.71 0.55 Oct 9 19:53= =0D=0A > IS> [..]=0D=0A > >> Proc: = Interrupts=0D=0A > >> r p d s w Csw T= rp Sys Int Sof Flt 24 cow 2008 total=0D=0A > >> 2 3 = 39 23k 67 563 9 1710 47 15 zfod 9 ata0 irq14=0D=0A= > >> ozfod = nfe0 irq23=0D=0A > >> 23.1%Sys 50.8%Intr 1.3%User 0.0%Nice 24.8%I= dle %ozfod 1999 cpu0: time=0D=0A > >> | | | | | |= | | | | | daefr=0D=0A > >> =3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D+++++++++++++++++++++++++> 6 prcfr=0D=0A >=20= =0D=0A > IS> Yes, system and esp. interrupt time is heavy .. 23k context = switches!?=0D=0A >=20=0D=0A > IS> In addition to b. f.'s good advice .. a= s you later said, 2000 Hz slicing=0D=0A > IS> _should_ be ok, unless a sl= ow CPU? Or perhaps a fast CPU throttled back=0D=0A > IS> too far .. powe= rd? Check sysctl dev.cpu.0.freq while this is happening.=0D=0A >=20=0D=0A= > IS> Disable p4tcc if it's a modern CPU; that usually hurts more than h= elps.=0D=0A > IS> Disable polling if you're using that .. you haven't pro= vided much info,=0D=0A > IS> like is this with any network load, despite = nfe0 showing no interrupts?=0D=0A=0D=0A > Polling is ON. Traffice is abou= t 60Mbit/s routed from nfe0 to vlan4 on rl0=0D=0A > when interrupts are h= appen traffic slow down to 25-30Mbit/s.=0D=0A=0D=0AOut of my depth. If i= t's a net problem - maybe not - you may do better=20=0D=0Ain freebsd-net@= if you provide enough information (dmesg plus ifconfig,=20=0D=0Avmstat -= i etc, normally and while this problem is happening).=0D=0A=0D=0A > There= is no p4tcc option in KERNEL config file.=0D=0A=0D=0ANo, it can be enabl= ed by cpufreq(4). See dmesg for acpi_throttle or=20=0D=0Ap4tcc, but it l= ooks like you might not have device cpufreq in your=20=0D=0Akernel or loa= ded, or dev.cpu.0.freq and more would have shown below.=0D=0A=0D=0A > dis= able/enable polling does not help. situation still same.=0D=0A=0D=0A > sy= sctl -a | grep freq=0D=0A > kern.acct_chkfreq: 15=0D=0A > kern.timecounte= r.tc.i8254.frequency: 1193182=0D=0A > kern.timecounter.tc.ACPI-fast.frequ= ency: 3579545=0D=0A > kern.timecounter.tc.TSC.frequency: 1809280975=0D=0A= > net.inet.sctp.sack_freq: 2=0D=0A > debug.cpufreq.verbose: 0=0D=0A > de= bug.cpufreq.lowest: 0=0D=0A > machdep.acpi_timer_freq: 3579545=0D=0A > ma= chdep.tsc_freq: 1809280975=0D=0A > machdep.i8254_freq: 1193182=0D=0A=0D=0A= Only useful for what it doesn't show :)=0D=0A=0D=0A > >> How to obtain w= hat nasty happen, which process take 36-50% of CPU=0D=0A > >> resource?=0D= =0A >=20=0D=0A > IS> Try 'top -S'. It's almost certainly system process[e= s], not shown above.=0D=0A=0D=0ADoes that not show anything? Also, somet= hing like 'ps auxww | less'=20=0D=0Ashould show you what's using all that= CPU. I'm out of wild clues.=0D=0A=0D=0Acheers, Ian=0D=0A_______________= ________________________________=0D=0Afreebsd-questions@freebsd.org maili= ng list=0D=0Ahttp://lists.freebsd.org/mailman/listinfo/freebsd-questions=0D= =0ATo unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebs= d.org"=0D=0A