On 03-11-2019 13:10, Achim Gratz via devel wrote: > based on the comments in the source. Again, if you don#t actually use > hardpps (and if this is the same Ryzen system you've had the timer > trouble on) it would be much more likely to work if you didn't configure > NTP_PPS and left the timer selection at the automoatic choice TSC > instead of forcing HPET.
When booting with hpet=disable we see stuff like: [ 49.411072] usb 1-6.3: new full-speed USB device number 4 using xhci_hcd [ 60.413459] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 60.413460] clocksource: 'acpi_pm' wd_now: 9efd1b wd_last: 4c447b mask: ffffff [ 60.413461] clocksource: 'tsc' cs_now: 46847f4e13 cs_last: 3d27b1ddd6 mask: ffffffffffffffff [ 60.413461] tsc: Marking TSC unstable due to clocksource watchdog [ 60.413473] usb 3-6.1: New USB device strings: Mfr=1, Product=3, SerialNumber=3 [ 60.413484] sdc: sdc1 sdc2 sdc4 [ 60.413931] ata6.00: Enabling discard_zeroes_data [ 60.414026] sd 5:0:0:0: [sdc] Attached SCSI removable disk [ 61.103005] usb 3-6.1: Product: 00 [ 61.103006] usb 3-6.1: Manufacturer: Moonbase Otago http://www.moonbaseotago.com/random [ 61.103007] usb 3-6.1: SerialNumber: 00 [ 61.103031] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 61.389493] sched_clock: Marking unstable (61145974825, -42941333)<-(61315108884, -212077652) [ 61.389516] Freeing unused kernel image (initmem) memory: 1056K I.e.: messages about TSC appear to be not too positive. Gigabyte customer support were informed about this. when running without HPET ntpd still does not select NMEA gps as system peer. So HPET is not the cause now. But what is? Kind regards, Udo _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
