From owner-freebsd-current@FreeBSD.ORG  Tue Mar  9 00:08:18 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 DCFB216A4CE
	for <current@freebsd.org>; Tue,  9 Mar 2004 00:08:18 -0800 (PST)
Received: from smtp.mho.com (smtp.mho.net [64.58.4.5])
	by mx1.FreeBSD.org (Postfix) with SMTP id 97E3443D5C
	for <current@freebsd.org>; Tue,  9 Mar 2004 00:08:18 -0800 (PST)
	(envelope-from scottl@freebsd.org)
Received: (qmail 81655 invoked by uid 1002); 9 Mar 2004 08:08:16 -0000
Received: from unknown (HELO ?10.4.1.17?) (64.58.1.252)
  by smtp.mho.net with SMTP; 9 Mar 2004 08:08:16 -0000
Date: Tue, 9 Mar 2004 01:11:15 -0700 (MST)
From: Scott Long <scottl@freebsd.org>
X-X-Sender: scottl@pooker.samsco.home
To: Alfred Perlstein <alfred@freebsd.org>
In-Reply-To: <20040309071912.GM56622@elvis.mu.org>
Message-ID: <20040309010921.Y61788@pooker.samsco.home>
References: <20040309071912.GM56622@elvis.mu.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 08:08:19 -0000

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?

Scott