From: "Régis Odeyé" <regis.odeye@kontron.com>
To: linuxppc-dev@ozlabs.org
Subject: 8641D, gianfar driver and BAD Interruptions
Date: Tue, 17 Nov 2009 17:42:01 +0100 [thread overview]
Message-ID: <4B02D259.6030905@kontron.com> (raw)
Hello,
On a board based on 8641D, we have BAD interruptions (cat
/proc/interrupts) which means spurious interruptions seen by the MPIC.
The number of this BAD ITs are increasing during the life time of the
system and depending on the ethernet activity.
So this seems to come from the gianfar and we experimented that:
- when we are binding the three interruptions enet_tx, enet_rx and
enet_err of each interfaces on the same processor, the BAD interruptions
do not increase any more.
- when we are compiling the driver without the NAPI mode, there is no
more BAD interruptions at all.
We are playing with a 2.6.25 + some patches Linux kernel.
I did not analyze the errata list of 8641D with this perspective but is
there anybody who get some inputs about the phenomenon ?
Regards.
--
Régis ODEYE
Kontron Modular Computers SA
150, rue M. Berthelot / ZI Toulon Est / BP 244 / Fr 83078 TOULON Cedex 9
Phone: (33) 4 98 16 34 86 Fax: (33) 4 98 16 34 01
E-mail: regis.odeye@kontron.com Web : www.kontron.com
reply other threads:[~2009-11-17 16:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B02D259.6030905@kontron.com \
--to=regis.odeye@kontron.com \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).