[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 Maxim Uvarov changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #13 from Ivan Khoronzhuk --- Sent series that combine previously mentioned updated patches: [lng-odp] [PATCH 0/3] add warnings to improve timer usage

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #12 from Ivan Khoronzhuk --- As were said previously we shouldn't set period less than resolution. It's incorrect and makes example to work in it's own time. The actual resolution of timer is not 1ns it's much

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #11 from Ivan Khoronzhuk --- Will send patch series soon to add fixes and corrections eliminating resolution impact demonstrated by previous comment and decreasing impact of schedule delays. -- You are

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #8 from Ivan Khoronzhuk --- What timer resolution? Could you please add init log. In my case it's 10ms. You are requesting 5us. Also we should forget timer accuracy +-1 timer tick. I need find some time to look

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #9 from Ivan Khoronzhuk --- *should -> shouldn't. Hands always forget about it... -- You are receiving this mail because: You are on the CC list for the bug.___

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #10 from Ivan Khoronzhuk --- The following correction allows to visually demonstrate resolution impact: [lng-odp] [PATCH v2 1/5] example: timer: print timer ticks/ns table instead of cycles/ns

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 Mike Holmes changed: What|Removed |Added Assignee|ola.liljed...@linaro.org

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #6 from Mike Holmes mike.hol...@linaro.org --- ./odp_timer_test -p 5 odp_timer_test.c:94:test_abs_timeouts(): [6] test_timeouts odp_timer_test.c:102:test_abs_timeouts(): [6] period 0 ticks, 5000 ns

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #4 from Ola Liljedahl ola.liljed...@linaro.org --- I see now that the reason for the abort and core dump is that the timeout period is smaller than the tick (the resolution of the timer). This does not make sense and is also not supported

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #5 from Ola Liljedahl ola.liljed...@linaro.org --- I am testing with periods 1x-2x the length of the timer resolution and still get intermittent too early failures. I assume this is caused by the non-determinism of Linux, the ODP threads

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 Mike Holmes mike.hol...@linaro.org changed: What|Removed |Added Ever confirmed|0 |1

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #3 from Ola Liljedahl ola.liljed...@linaro.org --- Not yet I am sorry. -- You are receiving this mail because: You are on the CC list for the bug. ___ lng-odp mailing list

[lng-odp] [Bug 1449] odp_timer_test core dump

https://bugs.linaro.org/show_bug.cgi?id=1449 --- Comment #1 from Ola Liljedahl ola.liljed...@linaro.org --- Does this error occur all of the time for the specific configuration (e.g. 5 CPU's?) or is this problem intermittent? I was thinking that if the test (it is just the timer example?) is