i have a new pentium D 820 (dual core), i'm using amd64 since it's 64bits, i don't know why my datetime is crazy, changing 2 seconds in past and to seconds in future again Reproducible: Always Steps to Reproduce: 1.check date and time values from system 2.check time from hardware clock 3.i don't know why but uptime is ok, if i check uptime it only add Actual Results: [root@spadim kernel]# date Ter Fev 6 13:44:58 BRST 2007 [root@spadim kernel]# date Ter Fev 6 13:44:56 BRST 2007 <-- time get back 2 seconds! [root@spadim kernel]# date Ter Fev 6 13:44:59 BRST 2007 <-- time continue ok [root@spadim kernel]# date Ter Fev 6 13:44:57 BRST 2007 <-- time get back 2 seconds! [root@spadim kernel]# date Ter Fev 6 13:45:00 BRST 2007 <-- time conttinue ok! my hw clock is ok see: [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:52 BRST -3.000384 segundos [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:53 BRST -0.174015 segundos [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:54 BRST -0.321278 segundos [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:55 BRST -0.366134 segundos [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:56 BRST -0.352971 segundos Ter 06 Fev 2007 13:47:12 BRST -0.292030 segundos [root@spadim kernel]# [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:47:16 BRST -3.220447 segundos <- system is 3 seconds slower? Linux version 2.6.19 gcc version 4.1.2 20061215 Expected Results: [root@spadim kernel]# date Ter Fev 6 13:44:58 BRST 2007 [root@spadim kernel]# date Ter Fev 6 13:44:58 BRST 2007 <-- should continue working ok [root@spadim kernel]# date Ter Fev 6 13:44:59 BRST 2007 <-- time continue ok [root@spadim kernel]# date Ter Fev 6 13:44:59 BRST 2007 <-- should continue working ok [root@spadim kernel]# date Ter Fev 6 13:45:00 BRST 2007 <-- time conttinue ok! my hw clock is ok see: [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:52 BRST -3.000384 segundos <- should be 0 seconds or <1 second [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:53 BRST -0.174015 segundos [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:54 BRST -0.321278 segundos [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:55 BRST -0.366134 segundos [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:46:56 BRST -0.352971 segundos Ter 06 Fev 2007 13:47:12 BRST -0.292030 segundos [root@spadim kernel]# [root@spadim kernel]# hwclock Ter 06 Fev 2007 13:47:16 BRST -3.220447 segundos <- system is 3 seconds slower? Linux version 2.6.19 gcc version 4.1.2 20061215 i don't know if it's a problem with cpu, since it's dual core i don't know if it can't hangle system time ok, since i have time based programs, i can't run any program, they get time values with (-1.233 seconds in past and stop working)
At least post your kernel version.
Linux version 2.6.19 gcc version 4.1.2 20061215 /proc/uptime have bug too! just uptime command don't [root@spadim proc]# cat /proc/uptime 153504.13 127890.61 [root@spadim proc]# cat /proc/uptime 153502.11 127891.04 [root@spadim proc]# cat /proc/uptime 153504.98 127891.42 [root@spadim proc]# cat /proc/uptime 153502.94 127891.84
(In reply to comment #2) > Linux version 2.6.19 Sigh; post emerge --info instead, not getting anywhere.
