Am Sonntag, 23. Dezember 2007 schrieb Gilles Chanteperdrix:
> Niklaus Giger wrote:
>  > a) The simulator fails in two tests with the vxworks skins. In
>  > 
> http://ngiger.dyndns.org/buildbot/builders/sim_f/builds/1/steps/check_sim/logs/stdio
>  > you will find at the end the lines
>  > > Some problems were reported in:
>  > > vxworks->t010726-1::
>  > > vxworks->t010823-2::
>  > Going back one finds:
>  > > starting VxWorks services.
>  > > Xenoscope: lt-t010823-2: fatal in MvmIrq (time=30000718.974563):
>  > > test interrupted by watchdog.
>  > and
>  > > starting VxWorks services.
>  > > Xenoscope: lt-t010726-1: fatal in MvmIrq (time=30000718.974820):
>  > > test interrupted by watchdog.
> 
> The problem is that the root task priority is 0, and that now, 0 is a
> priority with a special meaning. However, VxWorks priority range is from
> 0 to 255, not from 1 to 255.
> 
Usually only the excTask runs with priority 0 on a vxWorks system. I would
therefore suggest that we forbid starting a vxworks task with priority 0.
If a error is returned and this exception is documented in
the doc/txt/vxworks-skin.txt I could live with it without any problems.

Thanks anyway for your explanation.

-- 
Niklaus Giger

_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core

Reply via email to