public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001724] New: Thread stack overrun when high interrupt rate
Date: Mon, 07 Jan 2013 18:21:00 -0000 [thread overview]
Message-ID: <bug-1001724-777@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001724
Summary: Thread stack overrun when high interrupt rate
Product: eCos
Version: 3.0
Platform: All
OS/Version: Cortex-M
Status: UNCONFIRMED
Severity: major
Priority: low
Component: HAL
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: ml@tctechnologies.tc
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=2024)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=2024)
Description of bug and potential fix.
Interrupts can result in excessive (unbound) thread stack usage.
In certain cases an unbounded amount of stack is required for the threads to
handle DSR processing. That is not feasible and must be fixed.
The problem is described in the attached document.
We do have a patch fixing this which has been tested. It does solve the problem
with no side effects found so far.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-01-07 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 18:21 bugzilla-daemon [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-07 18:21 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=bug-1001724-777@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=unassigned@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).