From: Colin Ford <colin.ford@pipinghotnetworks.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Pseudo DSR's Not Working?
Date: Mon, 25 Sep 2000 04:54:00 -0000 [thread overview]
Message-ID: <39CF3CDC.EE1091A1@pipinghotnetworks.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Hello All,
I've been trying to figure out why my DSR's are not
working. I'm using the CVS version of eCos. I've tracked
it down to the alarm_thread (pseudo DSR). eCos seems to
deadlock when trying to aquire the mutex in cyg_splinternal?
The whole system just stops and nothing happens after the
call to cyg_splinternal because something else has the
mutex. I thought that at the moment the task tries to get the
mutex and can't the other threads should run. This does not
seem to be the case?
Does anyone else have the new pseudo DSR's working with
the network stack?
Many thanks,
Col.
--Â
===========================================
Colin Ford              PipingHot Networks
Software Engineer       +44 (0)1364 655510
Â
next reply other threads:[~2000-09-25 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-25 4:54 Colin Ford [this message]
2000-11-06 20:31 ` Jonathan Larmour
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=39CF3CDC.EE1091A1@pipinghotnetworks.com \
--to=colin.ford@pipinghotnetworks.com \
--cc=ecos-discuss@sources.redhat.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).