From owner-freebsd-current@FreeBSD.ORG Sun May 11 12:45:47 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 70D4537B401 for ; Sun, 11 May 2003 12:45:47 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA3AD43FB1 for ; Sun, 11 May 2003 12:45:46 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4BJjXkA008484; Sun, 11 May 2003 13:45:33 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 11 May 2003 13:45:04 -0600 (MDT) Message-Id: <20030511.134504.85393710.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <22333.1052574519@critter.freebsd.dk> References: <1052570246.27195.6.camel@cf.freebsd-services.com> <22333.1052574519@critter.freebsd.dk> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii 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: Sun, 11 May 2003 19:45:47 -0000 In message: <22333.1052574519@critter.freebsd.dk> "Poul-Henning Kamp" writes: : In message <1052570246.27195.6.camel@cf.freebsd-services.com>, Paul Richards wr : ites: : >I'm having real problems with current with heavy disk activity. : > : >When working in X and updating ports which causes a lot of disk activity : >I get *very* poor interactive responses. Keypresses can not appear for : >seconds and mouse movement is very jerky and unresponsive. : > : >I'm wondering if something is holding locks a long time in interrupt : >handlers and causing mouse/keyboard interrupts to be lost? : : We have this lock called "Giant" which we're trying to get rid off... Actually, this may be a problem in the acpi code. I have at least one battery that causes my system to 'freeze' for a while. The mouse interrupts aren't lost, per se, but just deferred too long. That was before the latest acpi upgrade, and I've not tried the offending battery since then (I think that the zero length messages are related to querrying the battery status, but haven't booted windows to find out for sure). Warner