From owner-freebsd-current@FreeBSD.ORG  Tue Nov 16 12:58:10 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 E511016A4CE
	for <current@freebsd.org>; Tue, 16 Nov 2004 12:58:10 +0000 (GMT)
Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 47F5743D64
	for <current@freebsd.org>; Tue, 16 Nov 2004 12:58:10 +0000 (GMT)
	(envelope-from mike@sentex.net)
Received: from localhost (localhost.sentex.ca [127.0.0.1])
	by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id iAGCw4EO049558;
	Tue, 16 Nov 2004 07:58:04 -0500 (EST)
	(envelope-from mike@sentex.net)
Received: from avscan1.sentex.ca ([127.0.0.1])
 by localhost (avscan1.sentex.ca [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 49417-02; Tue, 16 Nov 2004 07:58:03 -0500 (EST)
Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18])
	by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id iAGCw3Kr049540;
	Tue, 16 Nov 2004 07:58:03 -0500 (EST)
	(envelope-from mike@sentex.net)
Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27])
	by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id iAGCvuoi051127;
	Tue, 16 Nov 2004 07:57:57 -0500 (EST)
	(envelope-from mike@sentex.net)
Message-Id: <6.1.2.0.0.20041116080135.08dd3aa8@64.7.153.2>
X-Sender: mdtpop@64.7.153.2 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Tue, 16 Nov 2004 08:04:52 -0500
To: "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au>,
	current@freebsd.org
From: Mike Tancsa <mike@sentex.net>
In-Reply-To: <20041116001638.GC56252@squash.dsto.defence.gov.au>
References: <20041112054741.GY40520@squash.dsto.defence.gov.au>
 <6.1.2.0.0.20041115075917.12684480@64.7.153.2>
 <20041116001638.GC56252@squash.dsto.defence.gov.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: by amavisd-new
X-Virus-Scanned: by amavisd-new at avscan1b
Subject: Re: dealing with interupt 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, 16 Nov 2004 12:58:11 -0000

At 07:16 PM 15/11/2004, Wilkinson, Alex wrote:
>No, it is UP.

I would try disabling USB 2.0 and the sound in the BIOS if you are not 
using them.  Also, try commenting out

#device         apic            # I/O APIC

in your kernel.

On my machines, I can easily cause an interrupt storm by making a hardware 
device fire an interrupt that is not handled by the OS.  Not sure if it 
will help you, but its worth a shot.

         ---Mike