i try to move lock/unlock to macros and add some history logging.
Is possible next scenario:
1. task A lock mutex M
2. task A going to secondary mode
3. task A performing "long" io wait operation and some flags modified.
...
What do you mean by "some flags modified" ?
Anyway, the "scenario" you have described is just not how it all works.
BTW
at some moment i got a kernel oops, not very informative but...
...
Feb 9 23:26:02 dev-3 kernel: CPU: 0
Feb 9 23:26:02 dev-3 kernel: EIP: 0060:[<c01b53b2>] Not tainted VLI
Feb 9 23:26:02 dev-3 kernel: EFLAGS: 00210246 (2.6.17.14-xenomai #1)
Feb 9 23:26:02 dev-3 kernel: EIP is at remove_proc_entry+0x22/0x1b0
...
<c014476e> registry_proc_callback+0x17e/0x370
Does it happen at the time your application deletes some objects (e.g.
mutexes) ?
If it's not possible to get a simpler code fragment out of your
application to illustrate this problem, then maybe you could describe
some logic behind your application..
(how often each task acquires a lock / how long does it hold it and
what kind of actions does it do at this time, etc.)...
TIA,
--
Best regards,
Dmitry Adamushko
_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help
