From owner-freebsd-current@FreeBSD.ORG Sun May 11 18:49:24 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 700B937B401 for ; Sun, 11 May 2003 18:49:24 -0700 (PDT) Received: from mx0.freebsd-services.com (survey.codeburst.net [195.149.39.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9240043FBF for ; Sun, 11 May 2003 18:49:23 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from [192.168.7.2] (freebsd.gotadsl.co.uk [81.6.249.198]) by mx0.freebsd-services.com (Postfix) with ESMTP id 1B87C1B212; Mon, 12 May 2003 02:49:22 +0100 (BST) From: Paul Richards To: Andrew Gallatin In-Reply-To: <16062.59918.302092.929640@curly.cs.duke.edu> 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> Content-Type: text/plain Organization: Message-Id: <1052703871.4921.146.camel@cf.freebsd-services.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 12 May 2003 02:44:33 +0100 Content-Transfer-Encoding: 7bit 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 01:49:24 -0000 On Mon, 2003-05-12 at 01:25, Andrew Gallatin wrote: > Paul Richards writes: > > > > : > > > : I get boatloads of these, they stream past continuously. > > > : > > > : ACPI-0448: *** Error: AcpiEvGpeDispatch: No handler or method for > > > : GPE[0], disabling event > > <...> > > > No, it's a Supermicro DLE, with 2 P3-800 processors. > > > > > I've complained about these messages on my old DLE at least 3 times. > Nobody ever helped. > > I found that on my old DLE, the messages will stop if you unplug the > cable to the onboard fxp0 interface. They seem to happen each time > the device interrupts the host. These messages are a total DOS on a > server with a serial console, so I wouldn't be surprised if they > caused a perceptable slowdown on a box with a graphics head. > > Good luck getting an ACPI developer interested in it. I had no luck. > My advice is to just disable ACPI & forget about using it. As a further datapoint to my last email: 20 ?? WL 5:16.38 (irq9: fxp0 acpi0) I'll see if I can shift the interrupts around in the bios but I don't think I can since fxp is onboard. Perhaps acpi doesn't do anything to check whether the interrupt belongs to it or not and so when an fxp interrupt arrives the acpi handler gets called. -- Paul Richards