From owner-freebsd-current@FreeBSD.ORG Sun May 11 18:45:55 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 4DF5537B401 for ; Sun, 11 May 2003 18:45:55 -0700 (PDT) Received: from mx0.freebsd-services.com (survey.codeburst.net [195.149.39.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D8FB43FB1 for ; Sun, 11 May 2003 18:45:54 -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 0D7A81B211; Mon, 12 May 2003 02:45:53 +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: <1052703662.4921.142.camel@cf.freebsd-services.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 12 May 2003 02:41:04 +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:45:55 -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. Hmm, this is all starting to sound very familiar, because the fxp interface sometime stops responding as well and I have to reboot to make it start working again, even unloading and reloading the module doesn't help which points towards the hardware getting jammed and interrupts not happening. I wonder if something triggers an ACPI event when a packet arrives and that causes all these messages to be generated which causes a lock to be long enough for an fxp interrupt to be missed, which then confuses the fxp driver so it never clears it and leaves the card jammed. Maybe it's got something to do with ACPI watching the interrupt to wake up from suspend when a network packet arrives. Yhis is total speculation but it sounds plausible on paper :-) > Good luck getting an ACPI developer interested in it. I had no luck. > My advice is to just disable ACPI & forget about using it. Unfortunately if I disable acpi completely things are worse. The symptoms are a lot like a switch that isn't debounced, i.e. random multiples of keystrokes appear. -- Paul Richards