From owner-freebsd-current@FreeBSD.ORG Mon May 12 06:09:51 2003 Return-Path: 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 C892B37B401 for ; Mon, 12 May 2003 06:09:51 -0700 (PDT) Received: from mx0.freebsd-services.com (survey.codeburst.net [195.149.39.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B5C943F3F for ; Mon, 12 May 2003 06:09:51 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: by mx0.freebsd-services.com (Postfix, from userid 1002) id 1CC061B211; Mon, 12 May 2003 14:09:50 +0100 (BST) Date: Mon, 12 May 2003 14:09:49 +0100 From: Paul Richards To: Andrew Gallatin Message-ID: <20030512130949.GB48440@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> <16063.39366.930707.980678@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16063.39366.930707.980678@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4.1i 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2003 13:09:52 -0000 On Mon, May 12, 2003 at 08:55:34AM -0400, Andrew Gallatin wrote: > > 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.. Yeah, that email wasn't very clear. I moved fxp to irq10, so you're right, something else probably ended up on irq9. -- Paul Richards