public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Judong Kim <jdkim@snssol.co.kr>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Why does cyg_thread_delay() not return?
Date: Tue, 02 Aug 2005 23:50:00 -0000	[thread overview]
Message-ID: <1123026601.6848.36.camel@hermes> (raw)
In-Reply-To: <OFEPJEEHNEOHPACEGGNFGEIBCAAA.jdkim@snssol.co.kr>

On Wed, 2005-08-03 at 08:45 +0900, Judong Kim wrote:
> Hi everyone!!
> 
> I am working on network equipment, ecos-1.3.1-cvs and mpc850.
> 
> My problem is that cyg_thread_delay() function does not return, exactly Cyg_Scheduler::unlock() in cyg_thread_delay().
> But this is not all the time happened. Just, when network packets are flooded.
> 
> Now, I guess this is because of some kind of interrupts. But I am not sure.
> 
> Please, can anybody give some helps!

It could be interrupts, but it could be a number of things.
* Did you remember to include <cyg/kernel/kapi.h> in your program?
* Have you run the standard tests on your platform to make sure
  that interrupts, etc, are working?

Note: 1.3.1 is now more than 5 years old!  You really should
update to the latest code base.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-08-02 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 23:46 Judong Kim
2005-08-02 23:50 ` Gary Thomas [this message]
2005-08-03 14:01   ` [ECOS] " Grant Edwards

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=1123026601.6848.36.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jdkim@snssol.co.kr \
    /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).