From owner-freebsd-current@FreeBSD.ORG Tue Feb 3 21:33:17 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9475D8BD for ; Tue, 3 Feb 2015 21:33:17 +0000 (UTC) Received: from smtp2.wemm.org (smtp2.wemm.org [192.203.228.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp2.wemm.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A36DF3 for ; Tue, 3 Feb 2015 21:33:17 +0000 (UTC) Received: from overcee.wemm.org (canning.wemm.org [192.203.228.65]) by smtp2.wemm.org (Postfix) with ESMTP id 24360A6A for ; Tue, 3 Feb 2015 13:33:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=m20140428; t=1422999196; bh=Av+Bk9/8YGF0Fz1pOBJnPd8cPtmBYKyEam0JeULzjYI=; h=From:To:Subject:Date; b=pXrvqHgiyvn5oRpbuKvwo0giDDBMMaFqDlEACOz8pWs4wmVLznj6cXkltv4SaXCP5 oAa0tuPJn0QQcnZKIXh5u2HnyJw311IWpUGRcTdtwUyi1oIO8RT8EiGgdMa9DcNwkD wK7niVvrNTLw8t6Ws2/OUA4nORiOHqRcx2tpXnec= From: Peter Wemm To: 'freebsd-current' Subject: PSA: If you run -current, beware! Date: Tue, 03 Feb 2015 13:33:15 -0800 Message-ID: <8089702.oYScRm8BTN@overcee.wemm.org> User-Agent: KMail/4.14.2 (FreeBSD/11.0-CURRENT; KDE/4.14.2; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart27906425.LkZgOZNVXH"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 21:33:17 -0000 --nextPart27906425.LkZgOZNVXH Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" Sometime in the Dec 10th through Jan 7th timeframe a timing bug has bee= n=20 introduced to 11.x/head/-current. With HZ=3D1000 (the default for ba= re metal,=20 not for a vm); the clocks stop just after 24 days of uptime. This mean= s=20 things like cron, sleep, timeouts etc stop working. TCP/IP won't time = out or=20 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 uptim= e, you=20 may want to take precautions. A reboot prior to 24 days uptime (as hor= rible a=20 workaround as that is) will avoid it. Yes, this is being worked on. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI= 6FJV UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246 --nextPart27906425.LkZgOZNVXH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----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----- --nextPart27906425.LkZgOZNVXH--