On 11/07/2011 09:43 PM, Catalin Muresan wrote: > Salut, > > ati mai patit careva asa ceva (ouput din script-ul: while true ; do date > +%s.%N ; done): > > > 1320694673.099679358 > 1320694673.111291417 > 1320694673.099679358 > 1320694673.114144866 > 1320694673.099679358 > 1320694673.116983035 > 1320694673.115677103 > 1320694673.119778207 > 1320694673.115677103 > 1320694673.122541112 > 1320694673.115677103 > 1320694673.125251860 > 1320694673.115677103 > 1320694673.127989976 > 1320694673.115677103 > 1320694673.130696215 > 1320694673.131937749 > 1320694673.117001640 > 1320694673.134747499 > 1320694673.119767785 > 1320694673.137490678 > 1320694673.122615134 > 1320694673.140320151 > > > %s - seconds since 1970 > %N - nanoseconds. > > cum vedeti ceasul merge inainte si inapoi sau sta, cu efecte hilare gen > ping 0.000ms sau traceroute cu timpi negativi. > > CentOS 5.7, 2.6.18-238.9.1.el5 32bit. (la fel face si > cu kernel-2.6.18-238.12.1.el5) > > Vad urmatoarea chestie la boot: > > checking TSC synchronization across 2 CPUs: > CPU#0 had -403 usecs TSC skew, fixed it up. > CPU#1 had 403 usecs TSC skew, fixed it up. > > idei (in afara de maxcpu=1) ? ;) pentru inceput pune si tu un kernel din toamna asta. cel instalat e de centos 5.6, nu de 5.7
_______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
