| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 9 Jul 2009 14:58:37 -0700 From: john stultz <johnstul@...ibm.com> To: Stephen Hemminger <shemminger@...tta.com> Cc: Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org Subject: Re: Clock incorrect on 2.6.31-rc2 On Thu, Jul 9, 2009 at 2:10 PM, Stephen Hemminger<shemminger@...tta.com> wrote: > My system (desktop Ubuntu 9.0) runs fine with 2.6.30, but with 2.6.31-rc2 it does > not keep time correctly. Also ntptime reports an error. Can you better describe how it does not keep time? Is time moving too slow? too fast? Could you include output from the following commands with 2.6.31-rc2 (and 2.6.30 if you have the time). $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource $ dmesg $ ntpdc -c peers $ ntpdc -c kerninfo > $ ntptime > ntp_gettime() returns code 5 (ERROR) > time ce00daf1.8e997000 Thu, Jul 9 2009 14:09:05.557, (.557029), > maximum error 25016 us, estimated error 16 us > ntp_adjtime() returns code 5 (ERROR) > modes 0x0 (), > offset 0.000 us, frequency 7.827 ppm, interval 1 s, > maximum error 25016 us, estimated error 16 us, > status 0x40 (UNSYNC), > time constant 4, precision 1.000 us, tolerance 500 ppm, The error above just comes from NTP not being in sync. thanks -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists