odd clock jump messages from 0.2.0.21-rc

[Scott Bennett <bennett@xxxxxxxxxx>]

     Something weird seems to be happening several times a day since
I installed 0.2.0.21-rc.  The tor traffic drops to nothing suddenly
and a message is logged claiming that the system clock has jumped
forward some number of seconds and that all circuits are assumed to
be unusable.  (That assumption seems to me unwarranted for relatively
short jumps of the system clock, but that's a separate issue.)  In any
case, I haven't spotted any other evidence in my system that the clock
has indeed suddenly jumped forward.  Only tor is claiming that it has.
     Here are today's notice-level messages, beginning at the end of
the startup.

Mar 15 07:57:26.644 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Mar 15 07:57:29.385 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 15 07:58:22.455 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Mar 15 07:58:30.017 [notice] Performing bandwidth self-test...done.
Mar 15 14:05:55.095 [warn] Your system clock just jumped 111 seconds forward; assuming established circuits no longer work.
Mar 15 14:09:16.939 [warn] Your system clock just jumped 109 seconds forward; assuming established circuits no longer work.
Mar 15 15:25:55.299 [warn] TLS error while renegotiating handshake with [scrubbed]: sslv3 alert handshake failure (in SSL routines:SSL3_READ_BYTES)
Mar 15 16:20:32.468 [warn] Your system clock just jumped 104 seconds forward; assuming established circuits no longer work.
Mar 15 17:06:24.256 [warn] Your system clock just jumped 100 seconds forward; assuming established circuits no longer work.
Mar 15 17:21:23.752 [warn] Your system clock just jumped 162 seconds forward; assuming established circuits no longer work.
Mar 15 18:03:05.677 [warn] TLS error while renegotiating handshake with [scrubbed]: sslv3 alert handshake failure (in SSL routines:SSL3_READ_BYTES)
Mar 15 18:37:02.495 [warn] TLS error while renegotiating handshake with [scrubbed]: sslv3 alert handshake failure (in SSL routines:SSL3_READ_BYTES)
Mar 15 20:28:14.438 [warn] TLS error while renegotiating handshake with [scrubbed]: sslv3 alert handshake failure (in SSL routines:SSL3_READ_BYTES)
Mar 15 21:10:36.735 [warn] Your system clock just jumped 116 seconds forward; assuming established circuits no longer work.
Mar 15 23:27:50.720 [warn] Your system clock just jumped 116 seconds forward; assuming established circuits no longer work.

     I don't recall seeing these messages prior to 0.2.0.21-rc unless I did
something that would change the system clock.  What has changed that could
possibly be affecting tor's mechanism for determining whether it has been
unexpectedly dormant?


                                  Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet:       bennett at cs.niu.edu                              *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *
**********************************************************************