Since I add the watchdog option in my kernel configuration, The software 
doesn't block.
But I obtain an EPREM (-1) error on the second call of rtdm_event_timedwait, 
and in dmesg : Xenomai: assertion failed at 
kernel/xenomai/skins/rtdm/drvlib.c:919 (!xnpod_unblockable_p()).
I don't understand why I have this error, because the rtdm_event_timedwait is 
used as the 16550A rtserial rtdm driver. And I use this rtserial driver, and it 
works.
Note that this problem doesn't appears when I call rt_task_suspend just after 
my rtdm_event_timedwait, and I resume the task by a gets.

-----Message d'origine-----
De : Jan Kiszka [mailto:[EMAIL PROTECTED] 
Envoyé : mardi 13 mai 2008 18:59
À : DOURNES Guillaume
Cc : [email protected]
Objet : Re: [Xenomai-help] Interrupt management under rtdm driver

DOURNES Guillaume wrote:
> Sorry my old archive contained svn files. I send again my cource code.
> 
> I have some syslog message as kernel : Oops : 0000 [#1], or kernel : CPU : 0, 
> or EIP : 0060 [<f8a88de7>] Tainted : PF  VLI, etc.

Well, if your system locks up while the test runs, it is not likely that any 
message is pushed to syslog anymore. At best you see something on the console 
(VGA or serial).

> 
> I don't understand the watchdog catch. Can you explain a little more ?

See the help in the kernel configuration: If the the watchdog catches some 
spinning Xenomai thread, it will suspend it, allowing the rest of the system to 
run again. This will also generate a log message on the kernel console.

Jan

--
Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded 
Linux


_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to