From: gshan <gshan@alcatel-lucent.com>
To: michael@ellerman.id.au
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Kumar Gopalpet-B05799 <B05799@freescale.com>
Subject: Re: [HELP] BAD interrupts
Date: Thu, 24 Dec 2009 06:46:25 -0500 [thread overview]
Message-ID: <4B335491.1020203@alcatel-lucent.com> (raw)
In-Reply-To: <1261608230.3401.16.camel@concordia>
Michael Ellerman wrote:
> On Wed, 2009-12-23 at 19:41 +0530, Kumar Gopalpet-B05799 wrote:
>
>> Hi all,
>>
>> I am trying linux 2.6.32-rc3 in SMP mode. I am seeing a lot of BAD
>> interrupts when I do a "cat /proc/interrupts".
>>
>> I am running a forwarding application b/w two ethernet ports (ethernet
>> uses gianfar driver).
>>
>> Has any one observed these BAD interrupts ? If so, can someone help me
>> in understanding why these interrupts come and how to resolve it ?
>>
>
> You'll need to tell us what platform you're running on.
>
> The BAD interrupts come from ppc_spurious_interrupts. It's a count of
> the number of times we entered do_IRQ() (ie. took an external
> interrupt), but when we asked the interrupt controller which irq it was,
> the interrupt controller said there was no irq.
>
> Depending on your interrupt controller that might happen sometimes for
> valid reasons. Or it might indicate something is setup wrong.
>
> cheers
>
I think it will help to show us your /proc/interrupts so that how you
suffered
from bad interrupts.
next prev parent reply other threads:[~2009-12-23 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 14:11 [HELP] BAD interrupts Kumar Gopalpet-B05799
2009-12-23 14:11 ` Kumar Gopalpet-B05799
2009-12-23 22:43 ` Michael Ellerman
2009-12-24 11:46 ` gshan [this message]
2009-12-24 10:45 ` Kumar Gopalpet-B05799
2009-12-24 10:45 ` Kumar Gopalpet-B05799
2009-12-31 8:12 ` Régis Odeyé
-- strict thread matches above, loose matches on Subject: below --
2009-12-23 14:17 Kumar Gopalpet-B05799
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B335491.1020203@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=B05799@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.