From owner-freebsd-current@FreeBSD.ORG  Mon May 12 05:55:46 2003
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 B9FBB37B405
	for <current@freebsd.org>; Mon, 12 May 2003 05:55:46 -0700 (PDT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 594A243FA3
	for <current@freebsd.org>; Mon, 12 May 2003 05:55:45 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu
	[152.3.145.30])
	by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h4CCthMS011499
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 12 May 2003 08:55:43 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h4CCtZi00448;
	Mon, 12 May 2003 08:55:35 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16063.39366.930707.980678@grasshopper.cs.duke.edu>
Date: Mon, 12 May 2003 08:55:34 -0400 (EDT)
To: Paul Richards <paul@freebsd-services.com>
In-Reply-To: <20030512124753.GA48753@survey.codeburst.net>
References: <22333.1052574519@critter.freebsd.dk>
	<20030511.134504.85393710.imp@bsdimp.com>
	<1052684139.4921.3.camel@cf.freebsd-services.com>
	<20030511.143231.133432780.imp@bsdimp.com>
	<1052692357.4921.128.camel@cf.freebsd-services.com>
	<16062.59918.302092.929640@curly.cs.duke.edu>
	<1052703871.4921.146.camel@cf.freebsd-services.com>
	<16063.38255.961273.900146@grasshopper.cs.duke.edu>
	<20030512124753.GA48753@survey.codeburst.net>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
cc: current@freebsd.org
Subject: Re: Interrupt latency problems
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: Mon, 12 May 2003 12:55:47 -0000


Paul Richards writes:
 > 
 > I tried shifting the irq around last night, the bios does support this.
 > I definitely think there's something to this theory, when I put it on
 > irq 10 the problem got a whole lots worse to the point that the machine
 > couldn't be used and I had to reboot it (just error messages streaming
 > past on the console).
 > 
 > Unfortunately, I don't know what else was on irq10 at the time since
 > they move around when I change the bios settings.
 > 
 > I'm continuing to poke around to find out exactly what's causing
 > what....

I have this vague memory that the acpi always uses irq 9.  Perhaps
you inadvertently moved something else which generates more interrupts
onto irq 9..

Drew