Hi,

Thanks, I'll send a notification when there is further progress.

Cheers, Ludwig

Am 24. November 2014 14:06:52 MEZ, schrieb "Hiesgen, Raphael" 
<[email protected]>:
>Hello Ludwig,
>
>looks better. Some of the tests that did not work before, work fine
>now, e.g. using multiple timers.
>Setting a consecutive timer around 1 milliseconds still seem to end up
>in a freeze.
>Most often with the error: "schedule_timer(): timer is already due (3),
>mitigating.”.
>
>Thanks,
>Raphael
>
>> On Nov 22, 2014, at 4:08 PM, Ludwig Ortmann
><[email protected]> wrote:
>> 
>> Hi Raphael,
>> 
>> On Wed, Nov 19, 2014 at 06:51:25PM +0100, Ludwig Ortmann wrote:
>>> On Wed, Nov 19, 2014 at 05:12:42PM +0000, Hiesgen, Raphael wrote:
>>>> Hey there,
>>>> 
>>>> more questions! We encountered some problems using vtimer.  For
>once, setting multiple short timers consecutively leads to a segfault.
>We tired this with the timer_msg test reducing the intervals to around
>150ms.
>>>> 
>>>> A second problem showed up when setting multiple timers at once,
>e.g., from different threads. After a short time the "timer is already
>due” warning from schedule timer in hwtimer_cpu.c flashed and soon
>after the timers simply stopped.
>>>> 
>>>> So, I am not sure if these problems originate in our own
>implementation or the native port. In order to test the short timers,
>we executed the same program on the iot-lab_M3 board, where it worked
>even with much shorter timers. 
>>>> 
>>>> Anything I should know?
>>> 
>>> There is some problem I didn't get around to fixing, yes.
>>> I guess your issue it is related to this:
>>> https://github.com/RIOT-OS/RIOT/issues/715
>> 
>> Could you try if/how this changes the effect you are seeing in
>native?
>> 
>> https://github.com/RIOT-OS/RIOT/pull/2071
>> 
>> I am still able to freeze the timer (especially in Valgrind), but it
>> does so less often.
>> 
>> Cheers, Ludwig
>> _______________________________________________
>> devel mailing list
>> [email protected]
>> http://lists.riot-os.org/mailman/listinfo/devel
>
>_______________________________________________
>devel mailing list
>[email protected]
>http://lists.riot-os.org/mailman/listinfo/devel

_______________________________________________
devel mailing list
[email protected]
http://lists.riot-os.org/mailman/listinfo/devel

Reply via email to