From owner-freebsd-current@FreeBSD.ORG  Tue Mar  9 06:25:27 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 EFC7B16A4CE; Tue,  9 Mar 2004 06:25:27 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0EEF743D2D; Tue,  9 Mar 2004 06:25:27 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i29EPOIm033132;
	Tue, 9 Mar 2004 15:25:25 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Alfred Perlstein <alfred@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Tue, 09 Mar 2004 03:40:02 PST."
             <20040309114002.GN56622@elvis.mu.org> 
Date: Tue, 09 Mar 2004 15:25:24 +0100
Message-ID: <33131.1078842324@critter.freebsd.dk>
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 14:25:28 -0000

In message <20040309114002.GN56622@elvis.mu.org>, Alfred Perlstein writes:
>> > 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.

Try using the SW_WATCHDOG option.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.