Good morning everybody, here are some more news concerning the Xenomai crash issue. 1) I have tried to enable the CONFIG_DEBUG_SPINLOCK and CONFIG_DEBUG_SPINLOCK_SLEEP kernel config parameters. But I did not get any messages before the kernel freezes.
2) I have tried to link a static application (using -lstatic). When I pass the -L/usr/lib/nptl option to force the linker to use the nptl libs, the effect is the same. Well, I have now a static binary that freezes the system. I can mails you the binary file (about 280kByte bz2 file) if you like. I think this file is too large to be posted to the list. One additional question comes in my mind: As I learned from all that things that are related to the issue, it seems to be fairly critical to fork out of a real time task or to create new processes out of it. My question is now: Is it possible to force a real time task back to standard linux task behaviour, in this state the critical calls can be made. After it a move back to the origin real time state would be nice. In the native skin there is the rt_task_shadow() call that allows to move a standard linux task to a real time task. For moving a real time task to a standard task (and back) something like rt_task_movetostandard(&state) that saves the real time state in a variable and a rt_task_movebacktorealtime(&state) would be helpful. >From the user point all that would be something like a critical region, I enter a region where I can do really everything and then I move back to the real time domain. Regards Mathias -- Mathias Koehrer [EMAIL PROTECTED] Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer, nur 44,85 inkl. DSL- und ISDN-Grundgebühr! http://www.arcor.de/rd/emf-dsl-2 _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
