This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: Problems with "Scheduler lock not zero"
- From: Andrew Lunn <andrew at lunn dot ch>
- To: ?yvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: J?rgen Lambrecht <J dot Lambrecht at televic dot com>, eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 7 Nov 2006 23:31:27 +0100
- Subject: Re: [ECOS] Re: Problems with "Scheduler lock not zero"
- References: <c09652430611070722u281d3291sac51828f476aa014@mail.gmail.com> <4550AD75.9080306@televic.com> <c09652430611071304g378d9548wf4c99f0ae3c00fa3@mail.gmail.com>
Hi Folks
I think it is unlikley this is your problem, but i will mention it
anyway. I once had an assertion failure in the same place. It was
caused by a thread exiting with the scheduler locked.
Another thing to check is do you have an spurious interrupts. There
has been problems on the ARM platform not correctly dealing with
this. Since spurious interrupts generally means broken hardware, its
not the easiest thing to test and debug.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss