public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-bugs@ecos.sourceware.org
Subject: [Issue 1000660] ARM HAL breaks on spurious interrupt
Date: Mon, 15 Nov 2010 02:50:00 -0000 [thread overview]
Message-ID: <20101115024918.B49422F78006@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1000660-13@http.bugzilla.ecoscentric.com/>
Please do not reply to this email. Use the web interface provided at:
https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000660
Joe Porthouse <jporthouse@idexcorp.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jporthouse@idexcorp.com
--- Comment #2 from Joe Porthouse <jporthouse@idexcorp.com> 2010-11-15 02:49:15 GMT ---
Appears to have already been addressed in latest version.
Problem was present in eCos v2.0. When a spurious interrupt occurred,
interrupt_end() was never called and the scheduler was still locked on return
to the application.
In eCosPro v3.0.23, there are changes in the arm vectors.S file that
specifically address making sure the scheduler is unlocked when dealing with
spurious interrupts.
In /hal/arm/arc/current/src/vectors.S
// For a spurious interrupt, pass a NULL object. interrupt_end() will
// handle that and still unlock the scheduler.
Status on this issue should be closed.
--
Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.
You are on the CC list for the issue.
next parent reply other threads:[~2010-11-15 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1000660-13@http.bugzilla.ecoscentric.com/>
2010-11-15 2:50 ` bugzilla-daemon [this message]
2010-11-15 3:09 ` bugzilla-daemon
[not found] <bug-1000660-776@http.bugzilla.ecoscentric.com/>
2010-11-15 2:50 ` bugzilla-daemon
2010-11-15 3:09 ` bugzilla-daemon
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=20101115024918.B49422F78006@mail.ecoscentric.com \
--to=bugzilla-daemon@ecoscentric.com \
--cc=ecos-bugs@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).