From owner-freebsd-stable@FreeBSD.ORG Fri Apr 13 23:13:37 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 084591065675 for ; Fri, 13 Apr 2012 23:13:37 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 847438FC08 for ; Fri, 13 Apr 2012 23:13:36 +0000 (UTC) Received: by wibhj6 with SMTP id hj6so5972088wib.13 for ; Fri, 13 Apr 2012 16:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+iiMWqr13hz/CSEFo+bDkIlN0HQ+eVRk4Xsgv2Tf6sc=; b=ktwkTG64fvJYcH+SZcHeM2WEdMpvhpbfJ4U/lF04woFIBMF4iWbiaiKyegVwiy16ZS I2kDwtZnulBHQWesSyQUSvImkKw2Cb9FkeabKwyQD4gR5b+F/VlzDLI0FQ1F+BFVkT6v ohxS6i/FHoGy+ACuQXhpx30A+U9TJytrmM9JgVZwfqU93Ia/eNLe0r38WbNGbIqFvPAy 9K2xfMNs+FiZYuR1OKlsLkdhZQb/wUzydBFCXII8hiN034HJrMQzjHROeYrYbZf4ilxF E7AwclPOa0bMfIuqb6AP12KqFMfvD0MSSdtsnnArLoYZzN3d5UOLA2mZF4YEIWDPZxKi x5Ag== MIME-Version: 1.0 Received: by 10.180.82.136 with SMTP id i8mr46454wiy.19.1334358810458; Fri, 13 Apr 2012 16:13:30 -0700 (PDT) Received: by 10.216.190.219 with HTTP; Fri, 13 Apr 2012 16:13:30 -0700 (PDT) Received: by 10.216.190.219 with HTTP; Fri, 13 Apr 2012 16:13:30 -0700 (PDT) In-Reply-To: References: <4F6A67C0.7000909@sentex.net> <4F6B3B46.4060105@sentex.net> Date: Sat, 14 Apr 2012 08:43:30 +0930 Message-ID: From: Matt Thyer To: Freddie Cash Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org 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: Fri, 13 Apr 2012 23:13:37 -0000 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 ?