Re: Odd behaviour on recent boot of 11.1 with timecounters
On Sun, Dec 31, 2017 at 03:49:13PM +, 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 +, 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. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Odd behaviour on recent boot of 11.1 with timecounters
On Sun, Dec 31, 2017 at 04:51:47PM +0200, Konstantin Belousov wrote: > On Sun, Dec 31, 2017 at 02:17:08PM +, 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. Thanks, Gary Table 'FACP' at 0xddc1a6b0 Table 'APIC' at 0xddc1a7c0 APIC: Found table at 0xddc1a7c0 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 2 ACPI ID 2: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 4 ACPI ID 3: enabled SMP: Added CPU 4 (AP) MADT: Found CPU APIC ID 6 ACPI ID 4: enabled SMP: Added CPU 6 (AP) MADT: Found CPU APIC ID 1 ACPI ID 5: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 3 ACPI ID 6: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 5 ACPI ID 7: enabled SMP: Added CPU 5 (AP) MADT: Found CPU APIC ID 7 ACPI ID 8: enabled SMP: Added CPU 7 (AP) Copyright (c) 1992-2017 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.1-RELEASE-p6 #42 r327238: Wed Dec 27 17:55:36 GMT 2017 root@my:/usr/obj/usr/src/sys/MY amd64 FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) Table 'FACP' at 0xddc1a6b0 Table 'APIC' at 0xddc1a7c0 Table 'FPDT' at 0xddc1a858 Table 'MCFG' at 0xddc1a8a0 Table 'HPET' at 0xddc1a8e0 Table 'SSDT' at 0xddc1a918 Table 'DMAR' at 0xddc1c128 Table 'SSDT' at 0xddc1ace0 Table 'SSDT' at 0xddc1b690 ACPI: No SRAT table found PPIM 0: PA=0xb8000, VA=0x82a1, size=0x8000, mode=0 VT(vga): text 80x25 Preloaded elf kernel "/boot/kernel/kernel" at 0x8287f000. Preloaded /boot/entropy "/boot/entropy" at 0x8287fc48. Preloaded elf obj module "/boot/kernel/zfs.ko" at 0x8287fc98. Preloaded elf obj module "/boot/kernel/opensolaris.ko" at 0x82880500. Preloaded elf obj module "/boot/kernel/geom_mirror.ko" at 0x82880b30. Preloaded elf obj module "/boot/modules/nvidia-modeset.ko" at 0x82881220. Preloaded elf obj module "/boot/kernel/linux.ko" at 0x828817d0. Preloaded elf obj module "/boot/kernel/linux_common.ko" at 0x828820b8. Preloaded elf obj module "/boot/modules/nvidia.ko" at 0x828827e8. Calibrating TSC clock ... TSC clock: 3492136124 Hz CPU: Intel(R) Xeon(R) CPU E3-1270 V2 @ 3.50GHz (3492.14-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306a9 Family=0x6 Model=0x3a Stepping=9 Features=0xbfebfbffFeatures2=0x7fbae3ff AMD Features=0x28100800 AMD Features2=0x1 Structured Extended Features=0x281 XSAVE Features=0x1 VT-x: Basic
Re: Odd behaviour on recent boot of 11.1 with timecounters
On Sun, Dec 31, 2017 at 02:17:08PM +, 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. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Odd behaviour on recent boot of 11.1 with timecounters
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. Thanks, Gary ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"