Date: Mon, 9 Jan 2006 11:43:22 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-sparc64@freebsd.org Subject: Re: Getting rid of "Interrupt storm detected on "vec2024: puc0 puc1" Message-ID: <200601091143.23098.jhb@freebsd.org> In-Reply-To: <20060109151909.GB19485@SDF.LONESTAR.ORG> References: <20060109151909.GB19485@SDF.LONESTAR.ORG>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601091143.23098.jhb>