From owner-freebsd-stable@freebsd.org Sun Dec 31 16:47:51 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3747E86146 for ; Sun, 31 Dec 2017 16:47:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A9BA799B7; Sun, 31 Dec 2017 16:47:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id vBVGlc8p002864 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 31 Dec 2017 18:47:41 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua vBVGlc8p002864 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id vBVGlcQm002863; Sun, 31 Dec 2017 18:47:38 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 31 Dec 2017 18:47:38 +0200 From: Konstantin Belousov To: Gary Palmer Cc: freebsd-stable@freebsd.org Subject: Re: Odd behaviour on recent boot of 11.1 with timecounters Message-ID: <20171231164738.GY1684@kib.kiev.ua> References: <20171231141708.GA2629@in-addr.com> <20171231145147.GW1684@kib.kiev.ua> <20171231154913.GA63310@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171231154913.GA63310@in-addr.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2017 16:47:51 -0000 On Sun, Dec 31, 2017 at 03:49:13PM +0000, Gary Palmer wrote: > On Sun, Dec 31, 2017 at 04:51:47PM +0200, Konstantin Belousov wrote: > > On Sun, Dec 31, 2017 at 02:17:08PM +0000, Gary Palmer wrote: > > > > > > Hi, > > > > > > I recently updated to 11.1-RELEASE-p6 and on the most recent reboot > > > (after rebuilding all the necessary packages) the clock was running > > > slow and NTP wouldn't sync. I looked in /var/log/messages and I found > > > that for some reason, on this latest boot, it got the frequency of > > > TSC-low wrong. > > > > > > Aug 24 04:55:35 my kernel: Timecounter "TSC-low" frequency 1746073190 Hz quality 1000 > > > Aug 26 03:11:38 my kernel: Timecounter "TSC-low" frequency 1746070760 Hz quality 1000 > > > Aug 26 14:12:46 my kernel: Timecounter "TSC-low" frequency 1746075204 Hz quality 1000 > > > Nov 19 16:01:09 my kernel: Timecounter "TSC-low" frequency 1746070746 Hz quality 1000 > > > Dec 27 22:28:00 my kernel: Timecounter "TSC-low" frequency 1746074808 Hz quality 1000 > > > Dec 27 22:51:12 my kernel: Timecounter "TSC-low" frequency 1746071892 Hz quality 1000 > > > Dec 28 12:50:46 my kernel: Timecounter "TSC-low" frequency 1746069704 Hz quality 1000 > > > Dec 28 14:03:52 my kernel: Timecounter "TSC-low" frequency 1937876448 Hz quality 1000 > > > > > > Until the December reboots the machine was running 10.x. Dec 27 and later > > > are part of the process to get up to 11.x. > > > > > > Any idea why the TSC-low frequency jumped 191,806,744Hz on the last > > > measurement? > > > > > > I switched to HPET temporarily via sysctl and ntp seems happy. I'm just > > > concerned that the problem might recur on later reboots as TSC-low seems > > > to be the preferred timecounter. > > > > Show first 100 lines of the dmesg from a verbose boot. > > Also check BIOS settings related to overclocking and powersaving. > > > > Hi Konstantin, > > BIOS settings haven't been changed in 4+ years. No overclocking, and > all powersaving options are at "auto" or "disabled". > > The first 100 lines of verbose dmesg didn't seem that interesting so > I've included up to the end of "Device configuration finished" > > Note that this boot didn't have the TSC-low problem, and the boot > that had it wasn't verbose unfortunately. It is really the CPU identification which I wanted to see. You have IvyBridge, which is known to have good TSC. Try to obtain verbose dmesg with mis-identified frequency.