Date: Mon, 15 Nov 2004 15:23:49 +1030 From: "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au> To: current@freebsd.org Subject: Re: dealing with interupt storms ..... Message-ID: <20041115045349.GK51636@squash.dsto.defence.gov.au> In-Reply-To: <200411120946.iAC9kAsX008350@peedub.jennejohn.org> References: <alex.wilkinson@dsto.defence.gov.au> <20041112054741.GY40520@squash.dsto.defence.gov.au> <200411120946.iAC9kAsX008350@peedub.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Okay, well then why does top(1) display 85% CPU time dealing with interrupts ? - aW 0n Fri, Nov 12, 2004 at 10:46:10AM +0100, Gary Jennejohn wrote: "Wilkinson, Alex" writes: > Hi all, > > How does one stop an interrupt storm in RELENG_5 ? > > >From top(1) > > CPU states: 10.9% user, 0.0% nice, 3.9% system, 85.3% interrupt, 0.0% idle > > >From vmstat(1) > > total rate > ----- ---- > irq18: uhci2 bt0++ 9187313 426 > > 426 interrupts/sec isn't exactly a storm. I have 999/sec on my clock alone and see very low interrupt values in top. Is your top in step with your kernel? --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041115045349.GK51636>