[ECOS] Re: Problems with "Scheduler lock not zero"

["Øyvind Harboe" <oyvind dot harboe at zylin dot com>]

On 11/7/06, Jürgen Lambrecht <J.Lambrecht@televic.com> wrote:
> Hello Harboe,

I'm wondering.... What would be the observable effects of the
scheduler lock count not being zero if asserts weren't enabled?

If the answer is that everything, except timeslicing, would work just
fine, then I may have observed this on another project.

> I use again the MLQ scheduler instead of the bitmap and I have not seen
> the error again.

I'm using the MLQ scheduler and I do see the problem.

Perhaps you still have the problem, only more rarely?

It would not surprise me one bit if this problem is timing sensitive
and pretty much anything could make it come or go.

From my ecos.ecc:

cdl_component CYGSEM_KERNEL_SCHED_MLQUEUE {
   # Flavor: bool
   # No user value, uncomment the following line to provide one.
   # user_value 1
   # value_source default
   # Default value: 1


> My ecos is from feb 15 2006, so I have that patch from Nick.

I fetched a fresh version today, and the problem exists with our HAL &
CVS HEAD. Since this problem appears to be rare, I would suspect that
a) either our HAL is somehow provoking a rare problem or b) our HAL is
busted. We're using the opencores ethermac, otherwise it is basically
an EB40a.


As an experiment I disabled timeslicing(since I'm using pthreads this
requires a bit of hacking) and the problem persists.

--
Øyvind Harboe
http://www.zylin.com

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