From owner-freebsd-stable@freebsd.org Tue Jan 2 22:41:38 2018 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 A5CFAEBD3FE for ; Tue, 2 Jan 2018 22:41:38 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F65476B51; Tue, 2 Jan 2018 22:41:37 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w02MfV8l069712; Tue, 2 Jan 2018 14:41:37 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: , "Konstantin Belousov" In-Reply-To: <20180102164526.GA63396@in-addr.com> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Gary Palmer" Subject: Re: Odd behaviour on recent boot of 11.1 with timecounters Date: Tue, 02 Jan 2018 14:41:37 -0800 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable 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: Tue, 02 Jan 2018 22:41:38 -0000 On Tue, 2 Jan 2018 16:45:26 +0000 "Gary Palmer" said > On Sun, Dec 31, 2017 at 06:47:38PM +0200, Konstantin Belousov wrote: > > 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: > > > > >=20 > > > > > Hi, > > > > >=20 > > > > > I recently updated to 11=2E1-RELEASE-p6 and on the most recent rebo= ot=20 > > > > > (after rebuilding all the necessary packages) the clock was runni= ng=20 > > > > > slow and NTP wouldn't sync=2E I looked in /var/log/messages and I = found > > > > > that for some reason, on this latest boot, it got the frequency o= f > > > > > TSC-low wrong=2E > > > > >=20 > > > > > Aug 24 04:55:35 my kernel: Timecounter "TSC-low" frequency 174607= 3190 > > Hz quality 1000 > > > > > Aug 26 03:11:38 my kernel: Timecounter "TSC-low" frequency 174607= 0760 > > Hz quality 1000 > > > > > Aug 26 14:12:46 my kernel: Timecounter "TSC-low" frequency 174607= 5204 > > Hz quality 1000 > > > > > Nov 19 16:01:09 my kernel: Timecounter "TSC-low" frequency 174607= 0746 > > Hz quality 1000 > > > > > Dec 27 22:28:00 my kernel: Timecounter "TSC-low" frequency 174607= 4808 > > Hz quality 1000 > > > > > Dec 27 22:51:12 my kernel: Timecounter "TSC-low" frequency 174607= 1892 > > Hz quality 1000 > > > > > Dec 28 12:50:46 my kernel: Timecounter "TSC-low" frequency 174606= 9704 > > Hz quality 1000 > > > > > Dec 28 14:03:52 my kernel: Timecounter "TSC-low" frequency 193787= 6448 > > Hz quality 1000 > > > > >=20 > > > > > Until the December reboots the machine was running 10=2Ex=2E Dec 27 = and > > later > > > > > are part of the process to get up to 11=2Ex=2E > > > > >=20 > > > > > Any idea why the TSC-low frequency jumped 191,806,744Hz on the la= st > > > > > measurement? > > > > >=20 > > > > > I switched to HPET temporarily via sysctl and ntp seems happy=2E I= 'm > > just > > > > > concerned that the problem might recur on later reboots as TSC-lo= w > > seems > > > > > to be the preferred timecounter=2E > > > >=20 > > > > Show first 100 lines of the dmesg from a verbose boot=2E > > > > Also check BIOS settings related to overclocking and powersaving=2E > > > >=20 > > >=20 > > > Hi Konstantin, > > >=20 > > > BIOS settings haven't been changed in 4+ years=2E No overclocking, and > > > all powersaving options are at "auto" or "disabled"=2E > > >=20 > > > The first 100 lines of verbose dmesg didn't seem that interesting so > > > I've included up to the end of "Device configuration finished" > > >=20 > > > Note that this boot didn't have the TSC-low problem, and the boot > > > that had it wasn't verbose unfortunately=2E > >=20 > > It is really the CPU identification which I wanted to see=2E You have > > IvyBridge, which is known to have good TSC=2E >=20 > Ah >=20 > > Try to obtain verbose dmesg with mis-identified frequency=2E >=20 > Tried, and failed after 20+ reboots=2E I've left >=20 > boot_verbose=3D" -v" I believe that should read: boot_verbose=3D"YES" but maybe just the occurrence of something makes it a positive=2E >=20 > in /boot/loader=2Econf to catch any boot-time wonkiness and undone it at > runtime with=20 >=20 > debug=2Ebootverbose=3D0 >=20 > in /etc/sysctl=2Econf as I found that the snd_hda driver is =2E=2E=2E chatty > at runtime=2E >=20 > Thanks, >=20 > Gary > _______________________________________________ > freebsd-stable@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd=2Eorg"