i.am.meikle
Dabbler
- Joined
- Jul 11, 2012
- Messages
- 10
Hi,
My FreeNAS system time keeps leaping ahead in time.
It is currently 16:00 here in Norway, and my FreeNAS box says: Fri Jul 13 00:56:21 CEST 2012 !!!
It appears to be very similar behaviour to: http://forums.freenas.org/showthrea...ncrement-rapidly/page4&highlight=setting+time
>sysctl kern.timecounter.hardware
>kern.timecounter.hardware: ACPI-fast
>sysctl kern.timecounter.choice
>kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) dummy(-1000000)
>dmesg | grep -i time
>Timecounter "i8254" frequency 1193182 Hz quality 0
>Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
>acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
>pci0: <multimedia, HDA> at device 20.2 (no driver attached)
>acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
>Timecounter "HPET" frequency 14318180 Hz quality 900
>atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0
>Timecounters tick every 1.000 msec
I am using a Gigabyte GA-A75M-S2V motherboard (brand new).
My ntp servers are correctly setup and appear to be working until FreeNAS jumps into the future and then they report that the "time corrections exceeds sanity limit" and then refuse to reset the time. There does not appear to be a way of setting the time from the WebGUI.
I have powerd running. Not sure if this has anything to do with it.
I do not know what the different kern.timecounter.choice items are, so am a little reluctant to start playing with them until I get some more concrete info on their effect.
Any suggestions ?
Thanks
Ian
My FreeNAS system time keeps leaping ahead in time.
It is currently 16:00 here in Norway, and my FreeNAS box says: Fri Jul 13 00:56:21 CEST 2012 !!!
It appears to be very similar behaviour to: http://forums.freenas.org/showthrea...ncrement-rapidly/page4&highlight=setting+time
>sysctl kern.timecounter.hardware
>kern.timecounter.hardware: ACPI-fast
>sysctl kern.timecounter.choice
>kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) dummy(-1000000)
>dmesg | grep -i time
>Timecounter "i8254" frequency 1193182 Hz quality 0
>Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
>acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
>pci0: <multimedia, HDA> at device 20.2 (no driver attached)
>acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
>Timecounter "HPET" frequency 14318180 Hz quality 900
>atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0
>Timecounters tick every 1.000 msec
I am using a Gigabyte GA-A75M-S2V motherboard (brand new).
My ntp servers are correctly setup and appear to be working until FreeNAS jumps into the future and then they report that the "time corrections exceeds sanity limit" and then refuse to reset the time. There does not appear to be a way of setting the time from the WebGUI.
I have powerd running. Not sure if this has anything to do with it.
I do not know what the different kern.timecounter.choice items are, so am a little reluctant to start playing with them until I get some more concrete info on their effect.
Any suggestions ?
Thanks
Ian