Date: Thu, 16 Oct 2008 00:29:36 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: nazir <nazir.haron@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Interrupt storm detected on "irq10:"; throttling interrupt source Message-ID: <20081016072936.GA3574@icarus.home.lan> In-Reply-To: <9af66ccb0810160023k6b804628ubcd907301083cd93@mail.gmail.com> References: <9af66ccb0810151744m6dc9176cxcadecae2939ee05f@mail.gmail.com> <581062.74286.qm@web56804.mail.re3.yahoo.com> <20081016042034.GB99978@icarus.home.lan> <9af66ccb0810160023k6b804628ubcd907301083cd93@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 16, 2008 at 03:23:33PM +0800, nazir wrote: > On Thu, Oct 16, 2008 at 12:20 PM, Jeremy Chadwick <koitsu@freebsd.org> wrote: > > On Wed, Oct 15, 2008 at 06:17:56PM -0700, mdh wrote: > >> --- On Wed, 10/15/08, nazir <nazir.haron@gmail.com> wrote: > >> > From: nazir <nazir.haron@gmail.com> > >> > Subject: Interrupt storm detected on "irq10:"; throttling interrupt source > >> > To: freebsd-questions@freebsd.org > >> > Date: Wednesday, October 15, 2008, 8:44 PM > >> > Hi, > >> > > >> > I'm getting these on my HP-DL165 AMD Quad Qore > >> > > >> > interrupt storm detected on "irq10:"; throttling > >> > interrupt source > >> > >> What is on IRQ 10? You can determine this via the command: > >> `dmesg |grep irq` then look for the line for IRQ 10 which specifies what device is there. It could be a driver problem, or it could be that the hardware there is bunk. > >> - mdh > > > > vmstat -i output would also come in handy here. > > # vmstat -i > interrupt total rate > irq1: atkbd0 30 0 > irq10: ohci0 ohci+ 8265418 989 > irq33: mpt0 49348 5 > irq40: bge0 75482 9 > cpu0: timer 16431874 1968 > cpu2: timer 16424530 1967 > cpu3: timer 16424557 1967 > cpu1: timer 16424557 1967 > cpu4: timer 16424556 1967 > cpu6: timer 16424540 1967 > cpu7: timer 16424521 1967 > cpu5: timer 16424556 1967 > Total 139793969 16743 Can you provide full output of "dmesg"? It appears you have an OCHI USB controller that is going crazy with interrupts, but there may be more devices attached to IRQ 10 which could be responsible (I think that's what the "+" indicates). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081016072936.GA3574>