I have run across this problem too. It is because with Linux 2.4.18 (and
other
versions??) in certain circumstances, gettimeofday() is broken and will
jump
backwards. See http://kt.zork.net/kernel-traffic/kt20020708_174.html#1.
Is there any particular reason for this assert? If there is, maybe:
if (msecs 0) msecs = 0;
would be more suitable.
Seems like this is only used to calculate a rate to display on the screen.
Maybe we should just accept Linux's opinion that time is going backwards.
Eventually it should go forwards again. :-)
Cheers,
Colin
