Re: Clock Unsynchronized
pr...@cam.ac.uk (Patrick Welche) writes: >Feb 1 12:09:51 warbler ntpd[327]: kernel reports TIME_ERROR: 0x41: Clock >Unsynchronized >Hardware problem? It's a regular message telling that your clock isn't synchronized. This may happen after synchronization is lost and regained, but may also before time is synchronized for the first time. See also the ntp_adjtime man page: Possible states of the clock are: TIME_OK Everything okay, no leap second warning. TIME_INS``insert leap second'' warning. TIME_DEL``delete leap second'' warning. TIME_OOPLeap second in progress. TIME_WAIT Leap second has occurred. TIME_ERROR Clock not synchronized. There are many reasons to lose synchronisation, a hardware error is only one possibility. -- -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: Clock Unsynchronized
> On Mon, 28 Jan 2019 at 15:51, Patrick Welche wrote: > > > > Just noticed (NetBSD-8.99.26/amd64): > > > > ntpd[1575]: kernel reports TIME_ERROR: 0x4041: Clock Unsynchronized > > > > This is after a ntpdate which succeeded in catching up the 3/4 hour > > that clock was behind by. I haven't seen this error before... > > > > Is ACPI-Fast a good choice? (I didn't choose...) > > > > # sysctl kern.timecounter > > kern.timecounter.choice = TSC(q=-100, f=2666902400 Hz) clockinterrupt(q=0, > > f=100 Hz) ichlpcib0(q=1000, f=3579545 Hz) ACPI-Fast(q=1000, f=3579545 Hz) > > lapic(q=-100, f=266767233 Hz) i8254(q=100, f=1193182 Hz) dummy(q=-100, > > f=100 Hz) > > kern.timecounter.hardware = ACPI-Fast > > kern.timecounter.timestepwarnings = 0 On Mon, Jan 28, 2019 at 07:17:23PM +, Chavdar Ivanov wrote: > I remember having problems sometimes ago when my NetBSD machines were > around 8.99.25 or so (my timeserver is an RPI Model B still on > 8.99.2). I haven't had these problems for a while, but all my -current > machines are on 8.99.32. I just updated to Wednesday's 8.99.32, and saw it again: Feb 1 12:09:51 warbler ntpd[327]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Hardware problem? Cheers, Patrick
Re: Clock Unsynchronized
I remember having problems sometimes ago when my NetBSD machines were around 8.99.25 or so (my timeserver is an RPI Model B still on 8.99.2). I haven't had these problems for a while, but all my -current machines are on 8.99.32. Chavdar On Mon, 28 Jan 2019 at 15:51, Patrick Welche wrote: > > Just noticed (NetBSD-8.99.26/amd64): > > ntpd[1575]: kernel reports TIME_ERROR: 0x4041: Clock Unsynchronized > > This is after a ntpdate which succeeded in catching up the 3/4 hour > that clock was behind by. I haven't seen this error before... > > Is ACPI-Fast a good choice? (I didn't choose...) > > # sysctl kern.timecounter > kern.timecounter.choice = TSC(q=-100, f=2666902400 Hz) clockinterrupt(q=0, > f=100 Hz) ichlpcib0(q=1000, f=3579545 Hz) ACPI-Fast(q=1000, f=3579545 Hz) > lapic(q=-100, f=266767233 Hz) i8254(q=100, f=1193182 Hz) dummy(q=-100, > f=100 Hz) > kern.timecounter.hardware = ACPI-Fast > kern.timecounter.timestepwarnings = 0 > > > Cheers, > > Patrick --
Clock Unsynchronized
Just noticed (NetBSD-8.99.26/amd64): ntpd[1575]: kernel reports TIME_ERROR: 0x4041: Clock Unsynchronized This is after a ntpdate which succeeded in catching up the 3/4 hour that clock was behind by. I haven't seen this error before... Is ACPI-Fast a good choice? (I didn't choose...) # sysctl kern.timecounter kern.timecounter.choice = TSC(q=-100, f=2666902400 Hz) clockinterrupt(q=0, f=100 Hz) ichlpcib0(q=1000, f=3579545 Hz) ACPI-Fast(q=1000, f=3579545 Hz) lapic(q=-100, f=266767233 Hz) i8254(q=100, f=1193182 Hz) dummy(q=-100, f=100 Hz) kern.timecounter.hardware = ACPI-Fast kern.timecounter.timestepwarnings = 0 Cheers, Patrick
