2011/11/7 Catalin Muresan <catalin.mure...@gmail.com> > 2011/11/7 manuel "lonely wolf" wolfshant <wo...@prolinux.ro> > >> 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 >> > > Ai dreptare, pun si revin. > > Am pus 2.6.18-274.7.1.el5 simptomele persista:
# ping -c 10000 -i .01 <IP> |grep '0\.000' 64 bytes from: icmp_seq=405 ttl=123 time=0.000 ms 64 bytes from icmp_seq=665 ttl=123 time=0.000 ms 64 bytes from icmp_seq=966 ttl=123 time=0.000 ms 64 bytes from icmp_seq=1328 ttl=123 time=0.000 ms 64 bytes from icmp_seq=1348 ttl=123 time=0.000 ms 64 bytes from icmp_seq=2156 ttl=123 time=0.000 ms 64 bytes from icmp_seq=2654 ttl=123 time=0.000 ms 64 bytes from icmp_seq=2988 ttl=123 time=0.000 ms 64 bytes from icmp_seq=3650 ttl=123 time=0.000 ms 64 bytes from icmp_seq=4321 ttl=123 time=0.000 ms 64 bytes from icmp_seq=4405 ttl=123 time=0.000 ms 64 bytes from icmp_seq=5149 ttl=123 time=0.000 ms Nu e VM, e un AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ Si la fel cu timpul. Imi imaginez ca un procesor are un timp si alt procesor are alt timp. 1320704281.642964547 1320704281.641286008 1320704281.645986417 1320704281.644283083 1320704281.649032685 1320704281.647373670 1320704281.652072952 1320704281.650401290 se pot rezolva cu echo pit > /sys/devices/system/clocksource/clocksource0/current_clocksource default e tsc. ciudat _______________________________________________ RLUG mailing list RLUG@lists.lug.ro http://lists.lug.ro/mailman/listinfo/rlug
