From owner-freebsd-stable@FreeBSD.ORG Sun Apr 15 08:55:58 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9243106566B for ; Sun, 15 Apr 2012 08:55:58 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 334D18FC1E for ; Sun, 15 Apr 2012 08:55:58 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1SJL0a-0005YL-NX for freebsd-stable@freebsd.org; Sun, 15 Apr 2012 10:40:33 +0200 Received: from dhcp-077-251-052-224.chello.nl ([77.251.52.224] helo=pinky) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1SJL0b-0005u6-4L for freebsd-stable@freebsd.org; Sun, 15 Apr 2012 10:40:33 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org References: <4F6A67C0.7000909@sentex.net> <4F6B3B46.4060105@sentex.net> Date: Sun, 15 Apr 2012 10:40:31 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/11.62 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.7 X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_20 autolearn=disabled version=3.2.5 X-Scan-Signature: 66f4fda096222dd2b2010deb1ce817c5 Subject: Re: 157k interrupts per second causing 60% CPU load on idle system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2012 08:55:58 -0000 On Sat, 14 Apr 2012 01:13:30 +0200, Matt Thyer wrote: > On Apr 7, 2012 2:38 PM, "Matt Thyer" wrote: >> >> On 7 April 2012 14:31, Matt Thyer wrote: >>> Since moving the SATA 3 disk to the onboard Intel SATA 2 controller I'm > no longer having that disk evicted from the raidz2 pool with write errors > and I thought that the high interrupt rate issue had also been solved but > it's back again. >>> >>> This is on 8-STABLE at revision 230921 (before the new driver hit > 8-STABLE). >>> >>> So now I need to go back to trying to determine what the cause is. >>> >> vmstat -i has shown that the issue was on irq 16. >> >> Unfortunately there seems to be a lot of things on irq 16: >> >> $ dmesg | grep "irq 16" >> >> pcib1: irq 16 at device 1.0 on pci0 >> mps0: port 0xee00-0xeeff mem > 0xfbdfc000-0xfbdfffff,0xfbd80000-0xfbdbffff irq 16 at device 0.0 on pci1 >> vgapci0: port 0xff00-0xff07 mem > 0xfb400000-0xfb7fffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0 >> uhci0: port 0xfe00-0xfe1f irq 16 at > device 26.0 on pci0 >> pcib2: irq 16 at device 28.0 on pci0 >> pcib3: irq 16 at device 28.4 on pci0 >> atapci0: port > 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq > 16 at device 0.0 on pci3 >> >> Any idea how to isolate which bit of hardware could be triggering the > interrupts ? >> >> Unfortunately the only device I could remove would be the SuperMicro > AOC-USAS2-L8i (so yes I could eliminate that). >> >> My biggest problem right now is not knowing how to trigger the issue. >> >> At this stage I'm going to upgrade to 9-STABLE and see if it returns. > > The problem does not occur with 9-STABLE. > > Who knows what the problem was ? USB maybe ? Do you still have the same hardware on the same interrupts on 9-STABLE? Are there changes in the use of MSI(-X)?