https://bugs.linaro.org/show_bug.cgi?id=2309
--- Comment #9 from Ola Liljedahl <ola.liljed...@linaro.org> --- > Maybe some tick calculation over/under flows: > timer.c:253:handle_tmo():Wrong tick: expected 18446744073709551615 actual 92 $ bc bc 1.06.95 Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. obase=16 18446744073709551615 FFFFFFFFFFFFFFFF The problem is that the test program expects the timer to be cancelled (and thus have the tick value 0xffffffffffffffff) but instead the timer expired (with the tick value 92) and the test program received the timeout event. So possibly a race condition with the worker thread which cancelled the timer and the background timer thread which scans the timer array looking for expired timers. The error second message (wrong tick) is redundant and not entirely correct but does validate the first message (wrong status for fresh timeout). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
