Date: Tue, 03 Feb 2015 13:33:15 -0800 From: Peter Wemm <peter@wemm.org> To: 'freebsd-current' <freebsd-current@freebsd.org> Subject: PSA: If you run -current, beware! Message-ID: <8089702.oYScRm8BTN@overcee.wemm.org>
index | next in thread | raw e-mail
[-- Attachment #1 --] 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 freebsd.org 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 - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJU0T6bAAoJEDXWlwnsgJ4EAQEH/Aj28f1VBcmC1KWeOnyn64U1 buR0bSWsxT//Vw+TJEtIG7K+olNFHbCzE9u1iBGbCZbIE/KSy8XfBEDZizTbIUmG +2jlSqv/DIN2GKza/X+ada9qy24Lg1LC4HaYjPE2kT3L44W0xilXW/C+ltlWaqcW p1rQ7Q0Uaew3wq6fd33FyiZ3edW0Gs1PMPmJS2naWjXf/VyBr7BuJZskJozwwt9B kMsBSniOf8hA9mHSZNDbSY2+nLKQcxJ4iG7MOaEdTMaG/hGE+JEtdob1c7hA3K5C dPo1PJZi/nW6IFiuPoWXMuUp5t3mFAyTO/hxEw4nv1eyItXfWHin6HMJIn6Hvbo= =Q3xS -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8089702.oYScRm8BTN>