Sometime in the Dec 10th through Jan 7th timeframe a timing bug has been 
introduced to 11.x/head/-current.    With HZ=1000 (the default for bare metal, 
not for a vm); the clocks stop just after 24 days of uptime.  This means 
things like cron, sleep, timeouts etc stop working.  TCP/IP won't time out or 
retransmit, etc etc.  It can get ugly.

The problem is NOT in 10.x/-stable.

We hit this in the cluster, the builds that we used are:
FreeBSD 11.0-CURRENT #0 r275684: Wed Dec 10 20:38:43 UTC 2014 - fine
FreeBSD 11.0-CURRENT #0 r276779: Wed Jan  7 18:47:09 UTC 2015 - broken

If you are running -current in a situation where it'll accumulate uptime, you 
may want to take precautions.  A reboot prior to 24 days uptime (as horrible a 
workaround as that is) will avoid it.

Yes, this is being worked on.
Peter Wemm -;;; KI6FJV
UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to