Hi!
-----Mensaje original----- De: arch-general-bounces@archlinux.org [mailto:arch-general- bounces@archlinux.org] En nombre de David C. Rankin Enviado el: jueves, 10 de noviembre de 2011 21:44 Para: General Discussion about Arch Linux Asunto: Re: [arch-general] linux 3.1-4 - two i686 lockups after ~ 5 hours of operations. two x86_64 seem OK
On 11/10/2011 01:55 PM, Mauro Santos wrote:
On 10-11-2011 19:16, David C. Rankin wrote:
Richard, David - check your hardware clock "# hwclock -r" and compare that to the time returned by "# date". If they are hours apart, then make sure your sysclock is correct and set the hardware clock to your sysclock with "# hwclock -w". Worth checking regardless. I know this used to be done on boot or shutdown and I don't know why it isn't anymore. I'll do some more digging.
You should take into account that 'hwclock -r' and 'date' might return different times and things will still be ok, it all depends on if you have the clock set to UTC or localtime and your timezone. The man page says there is some autodetection logic but as with all things it can fail.
True, hwclock always returns time in 'localtime' as does 'date'. Both also provide the '-u' option to return UTC. This box has the hwclock set to localtime because it dual-boots with M$. Come to think about it, it is one of my only boxes that is dual-boot. I wonder if the rtc set to localtime may be uncovering a regression that is causing this strange behavior, because honestly I can't explain jumping backwards in time over 13.75 hours with ntp running??
You can configure Windows to use UTC. It is explained in https://wiki.archlinux.org/index.php/Rc.conf Regards, Guillermo Leira