From: "Trenton D. Adams" <tadams@theone.dnsalias.com>
To: "'eCos Discussion'" <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] spurious interrupt occuring for no apparent reason
Date: Mon, 27 Aug 2001 11:58:00 -0000 [thread overview]
Message-ID: <000c01c12f28$4168a960$090110ac@TRENT> (raw)
I'm running on and edb7111-2 rev b board. Every once in awhile (once in
a blue moon), I get a spurious interrupt occuring.
TRACE: <5>[202]hal_arch_default_isr() Interrupt: 8
ASSERT FAIL: <5>[204]hal_arch_default_isr() Spurious Interrupt!!!
My program does not enabled EINT3 (int 8) in any way shape or form. The
edb7111-2 ethernet driver for the CS-8900 does enable this interrupt
though. But all it appears to do is IGNORE it. By this I mean simply
ack it and then re-enable it. So, this EINT3 problem should
theoretically never occur, should it?
Trenton D. Adams
Extreme Engineering
#17, 6025 - 12 St. SE
Calgary, Alberta, Canada
T2H 2K1
Phone: 403 640 9494 ext-208
Fax: 403 640 9599
http://www.extremeeng.com
next reply other threads:[~2001-08-27 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 11:58 Trenton D. Adams [this message]
2001-08-27 13:18 Dan Conti
2001-08-27 13:28 ` Trenton D. Adams
2001-08-27 13:46 Dan Conti
2001-08-27 14:05 ` Trenton D. Adams
2001-09-06 13:20 ` Jonathan Larmour
2001-09-13 9:41 ` Trenton D. Adams
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='000c01c12f28$4168a960$090110ac@TRENT' \
--to=tadams@theone.dnsalias.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).