[Bug 693] Invalid timeval passed to setitmer()

bugzilla-daemon at bugzilla.openmoko.org bugzilla-daemon at bugzilla.openmoko.org
Tue Oct 9 13:28:59 CEST 2007


ticktock35 at gmail.com changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

------- Additional Comments From ticktock35 at gmail.com  2007-10-09 13:28 -------
After verify thr properities of setitimer. setitimer works well even when system
is changing.
And so that the log shows that it's a racing condition: when registering a
timer, gsmd get the expire time and then the current time changed before
calculate the diff(calc_next_expireation). And so that the diff happened at past.
If a system is too busy or changing system, this kind of errors may happen, so
that a second chance may needed. Because "diff" is calculated from the closest
timeout, it is reasonable to assume this one is closest timer.

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the buglog mailing list