From owner-freebsd-current@FreeBSD.ORG Fri Jul 23 18:16:16 2004 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 F074416A4CE for ; Fri, 23 Jul 2004 18:16:16 +0000 (GMT) Received: from smtp05.web.de (smtp05.web.de [217.72.192.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id 969D243D4C for ; Fri, 23 Jul 2004 18:16:16 +0000 (GMT) (envelope-from nakal@web.de) Received: from [217.81.253.50] (helo=[217.81.253.50]) by smtp05.web.de with esmtp (TLSv1:DES-CBC3-SHA:168) (WEB.DE 4.101 #44) id 1Bo4ad-0005Tf-00 for freebsd-current@freebsd.org; Fri, 23 Jul 2004 20:16:15 +0200 From: Martin To: FreeBSD Current Content-Type: text/plain Message-Id: <1090606572.2670.15.camel@klotz.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 23 Jul 2004 20:16:13 +0200 Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de Subject: Problems with interrupts on -CURRENT? 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: Fri, 23 Jul 2004 18:16:17 -0000 Hi, I have a kernel from Mon Jul 19 01:06:15 CEST 2004 and it's terribly slow, especially while executing applications in parallel. Following symptoms: - mouse cursor is non-responsive for 3-5 seconds - hard-disk is slow and is unusually active (portupgrade needs about 15 minutes till it arrives compiling first port) - printing is slowed down a single line needs about 10 seconds - syncer is slowly counting vnodes down and needs a few seconds till it arrives at 0 I have also discovered this, after starting the print job: Jul 23 19:35:32 Interrupt storm detected on "irq7: lpt0"; throttling interrupt source Remarks about my -CURRENT kernel: I have played with some kernel settings earlier: - SCHED_4BSD, because UPDATING said so - DEVICE_POLLING is now off in this kernel I'm just reporting it, because it might be related with the instability issues, which you mention here. Any ideas what I should do now? Martin