From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 9 18:31:56 2006 Return-Path: X-Original-To: freebsd-sparc64@freebsd.org Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35DFE16A41F for ; Mon, 9 Jan 2006 18:31:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24BA743D45 for ; Mon, 9 Jan 2006 18:31:53 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5635824 for multiple; Mon, 09 Jan 2006 13:33:25 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k09IVm7l057228; Mon, 9 Jan 2006 13:31:49 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-sparc64@freebsd.org Date: Mon, 9 Jan 2006 11:43:22 -0500 User-Agent: KMail/1.8.2 References: <20060109151909.GB19485@SDF.LONESTAR.ORG> In-Reply-To: <20060109151909.GB19485@SDF.LONESTAR.ORG> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601091143.23098.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1235/Sun Jan 8 13:13:01 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: Getting rid of "Interrupt storm detected on "vec2024: puc0 puc1" X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2006 18:31:56 -0000 On Monday 09 January 2006 10:19 am, Bruce O'Neel wrote: > Hi, > > I get the following message: > > Interrupt storm detected on "vec2024: puc0 puc1"; > throttling interrupt source > > and then, suprise suprise, the mouse quits working in X. Sadly X is > less functional without a mouse. > > I think the problem is the null modem cable to a sparc20 console. > > Is there: > > - an easy way to say "ok, I think I've fixed the problem, can we > start over" short of rebooting? If the interrupt stops storming the ithread code will notice and stop throttling it. It only throttles the source to hz interrupts per second while the storm is active. > - an easy way to know what might be wrong? Is there some way to see > the interrupt rate so that I could know if unplugging the console cable > fixes it? vmstat -i will show you the interrupt counts. systat -vmstat can give a better since of the current rates. Probably there's a bug in a driver in that the device is signalling a condition the driver doesn't handle, so the interrupt is never handled from the device's perspective. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org