| 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
| ||
|
Message-ID: <75b66ecd0801251529s341ab6f6n2c8c56850b9ba883@mail.gmail.com> Date: Fri, 25 Jan 2008 18:29:58 -0500 From: "Lee Revell" <rlrevell@...-job.com> To: "Michael Tokarev" <mjt@....msk.ru> Cc: Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: tickless/dynticks + cpufreq = tsc unstable On Jan 25, 2008 6:02 PM, Michael Tokarev <mjt@....msk.ru> wrote: > Is it normal that once I enable cpufreq on > a tickless system, it spews a warning: > > Clocksource tsc unstable (delta = -288201154 ns) > > ? Yes, it's normal. Dual core AMD64 machines really do have unstable TSC. Lee -- 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