* Fw: MPC8260 bad interrupts
@ 2004-02-09 11:24 Ing.Gianfranco Morandi (LAN)
0 siblings, 0 replies; only message in thread
From: Ing.Gianfranco Morandi (LAN) @ 2004-02-09 11:24 UTC (permalink / raw)
To: LinuxPPC
> Jon Diekema wrote:
> This problem was discussed on mailing list before also and you can
> eliminate this problem by inserting a sync instruction at a certain
> place in the 8260 interrupt handling code. See, for example,
I had the same problem with our custom driver, and the patch eliminated the
problem.
After a double check on our code we found a small bug over a possible race
condition.
After fixed the bug we removed the sync instruction and bad interrupt never
happened again.
My personal suggestion is:
1 - have a look to the mail thread then you will discover that this problem
occours only with centain kernel revision;
2 - double check your code to be sure that you do not have any race
condition;
3 - check your hardware init sequence;
4 - finally apply the patch (only in you do not have any better solution).
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-02-09 11:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-09 11:24 Fw: MPC8260 bad interrupts Ing.Gianfranco Morandi (LAN)
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).