This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Assertion generated for Scheduler lock == 0

From: sandeep <sandeep at codito dot com>
To: radhakrishnan R <radhaamanji at yahoo dot co dot uk>
Cc: ecos-discuss at sources dot redhat dot com
Date: Sat, 20 Sep 2003 17:06:54 +0900
Subject: Re: [ECOS] Assertion generated for Scheduler lock == 0
References: <20030920051146.61264.qmail@web60001.mail.yahoo.com>

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

References:
- Assertion generated for Scheduler lock == 0
  - From: radhakrishnan R

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]