RE: [microblaze-uclinux] kernel BUG at sched.c:687!

[Brettschneider Falk <fbrettschneider@xxxxxxxxxxxxxxxxx>]

Hi,

Alejandro Lucero wrote:
> I assumed you are using the entry.S without my patch reported 
> two days ago. 
> aren't you?
I've tried JWs version of your patch but it doesn't help as a bugfix. My
environment is one active user app with several threads (SCHED_RR), a high
IRQ frequency (about 2 per millisecond), many thread switches, many
locks/unlocks of semaphores and mutexes. From time to time one thread of
that application calls pthread_cancel() to another thread. 
Often (about after 20 kill actions) this leads to either a Linux crash (with
several versions of "kernel BUG at sched.c:***"), or just a total hang or an
exit of the app with return code 5. (The statistical distribution is:
displaying of scheduler bug = 0,01%, Linux hang = 60%, process exit = rest.)
I haven't the problems if either the IRQ frequency is very low or no threads
are cancelled(). That's why I asked you if you ever tried to kill threads in
your application, this increases the chance of a Linux crash extremely here.

Cheers, F@lk
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/