public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] Assertion generated for Scheduler lock == 0
@ 2003-09-20  5:11 radhakrishnan R
  2003-09-20 11:26 ` sandeep
  0 siblings, 1 reply; 2+ messages in thread
From: radhakrishnan R @ 2003-09-20  5:11 UTC (permalink / raw)
  To: ecos-discuss

Hi,
   Iam executing the stress threads available under
kernel package.
   I have got the following assertion message.
"
INFO:<Stress threads test compiled on Sep 20 2003>
ASSERT FAIL: <16>smp.hxx [ 459] static void
Cyg_Scheduler_SchedLock::set_sched_lock() Scheduler
lock == 0
"

 From the above message , i observed that the
sched_lock variable is 0 and new_lock is Non zero
value. hence the assertion is generated.

Any debugging technique to trace this problem will be
helpfull.

Regards,
Radhakrishnan R

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ECOS] Assertion generated for Scheduler lock == 0
  2003-09-20  5:11 [ECOS] Assertion generated for Scheduler lock == 0 radhakrishnan R
@ 2003-09-20 11:26 ` sandeep
  0 siblings, 0 replies; 2+ messages in thread
From: sandeep @ 2003-09-20 11:26 UTC (permalink / raw)
  To: radhakrishnan R; +Cc: ecos-discuss


radhakrishnan R wrote:

> Hi,
>    Iam executing the stress threads available under
> kernel package.
>    I have got the following assertion message.
> "
> INFO:<Stress threads test compiled on Sep 20 2003>
> ASSERT FAIL: <16>smp.hxx [ 459] static void
> Cyg_Scheduler_SchedLock::set_sched_lock() Scheduler
> lock == 0
> "
> 
>  From the above message , i observed that the
> sched_lock variable is 0 and new_lock is Non zero
> value. hence the assertion is generated.
> 
> Any debugging technique to trace this problem will be
> helpfull.


what architecture you are working on? some of the scheduler related goes into HAL. may be something is messed up there?


-- 
regards
sandeep
--------------------------------------------------------------------------
They're only trying to make me LOOK paranoid!
--------------------------------------------------------------------------


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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-09-20 11:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-20  5:11 [ECOS] Assertion generated for Scheduler lock == 0 radhakrishnan R
2003-09-20 11:26 ` sandeep

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).