From owner-freebsd-current@FreeBSD.ORG  Tue Mar  9 10:19:39 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 01CEC16A4CE
	for <current@freebsd.org>; Tue,  9 Mar 2004 10:19:39 -0800 (PST)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EDAD243D2D
	for <current@freebsd.org>; Tue,  9 Mar 2004 10:19:38 -0800 (PST)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id E64405C7EE; Tue,  9 Mar 2004 10:19:38 -0800 (PST)
Date: Tue, 9 Mar 2004 10:19:38 -0800
From: Alfred Perlstein <alfred@freebsd.org>
To: Doug White <dwhite@gumbysoft.com>
Message-ID: <20040309181938.GP56622@elvis.mu.org>
References: <20040309071912.GM56622@elvis.mu.org>
	<20040309095540.U69332@carver.gumbysoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040309095540.U69332@carver.gumbysoft.com>
User-Agent: Mutt/1.4.2.1i
cc: current@freebsd.org
Subject: Re: diagnosing interrupt storms?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2004 18:19:39 -0000

* Doug White <dwhite@gumbysoft.com> [040309 09:57] wrote:
> On Mon, 8 Mar 2004, Alfred Perlstein wrote:
> 
> > At a certain point after booting my SMP 5-current box gets all
> > weird, typically I see 50%+ time spent in interrupt.  If I run "top
> > -S" I typically see one of the ithreads using 50% cpu.
> >
> > I'm trying to figure out what it's doing, what has gone wrong etc.
> >
> > Are there any sysctls to look at or things I can do to diagnose
> > this?
> 
> vmstat -i is useful for figuring out exactly which interrupt is storming,
> although the ithread might hint it too.
> 
> Which one is it?

It's typically been em (intel gigE) or the sound interrupt.

-- 
- Alfred Perlstein
- Research Engineering Development Inc.
- email: bright@mu.org cell: 408-480-4684