From owner-freebsd-current@FreeBSD.ORG  Tue Mar  9 03:40:02 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 8879316A4CE; Tue,  9 Mar 2004 03:40:02 -0800 (PST)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7FD2043D2D; Tue,  9 Mar 2004 03:40:02 -0800 (PST)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 7AF715C7E0; Tue,  9 Mar 2004 03:40:02 -0800 (PST)
Date: Tue, 9 Mar 2004 03:40:02 -0800
From: Alfred Perlstein <alfred@freebsd.org>
To: Scott Long <scottl@freebsd.org>
Message-ID: <20040309114002.GN56622@elvis.mu.org>
References: <20040309071912.GM56622@elvis.mu.org>
	<20040309010921.Y61788@pooker.samsco.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040309010921.Y61788@pooker.samsco.home>
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 11:40:02 -0000

* Scott Long <scottl@freebsd.org> [040309 00:08] 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?
> >
> > (also I my laptop still can't boot with top-of-the-tree current) :(
> >
> 
> A dmesg here would help, of course.  You might have a similar problem as
> me, where the SMI interrupt is misconfigured as active-low instead of
> active-high, so it storms the system.  Does disabling ACPI make a
> difference?  Since it's SMP, does disabling APIC (and thus turning it into
> UP) make a difference?

dmesg doesn't report anything out of the ordinary.

I will try your suggestions the next time I get wedged.

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