From: "Ing.Gianfranco Morandi (LAN)" <gianfranco.morandi@euro-studio.it>
To: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Fw: MPC8260 bad interrupts
Date: Mon, 9 Feb 2004 12:24:46 +0100 [thread overview]
Message-ID: <006501c3eeff$536fe8a0$0400a8c0@portatile> (raw)
> 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/
reply other threads:[~2004-02-09 11:24 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='006501c3eeff$536fe8a0$0400a8c0@portatile' \
--to=gianfranco.morandi@euro-studio.it \
--cc=linuxppc-embedded@lists.linuxppc.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).