| 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, 29 Nov 2007 09:56:39 +0200 (EET) From: Tero Roponen <teanropo@....fi> To: johnstul@...ibm.com, tglx@...utronix.de cc: linux-kernel@...r.kernel.org Subject: TSC blacklisting is unneeded? Hi, In January 2006 I had problems with the TSC clocksource, that were fixed by adding a blacklist: http://lkml.org/lkml/2006/1/19/362 Recently I tested 2.6.24-rc3-git1 by commenting out the only entry in the bad_tsc_dmi_table, and everything still worked without it: --- dmesg.with 2007-11-28 10:58:21.000000000 +0200 +++ dmesg.without 2007-11-28 11:08:10.000000000 +0200 @@ -31,8 +31,7 @@ -Detected 265.284 MHz processor. -IBM Thinkpad 380XD detected: marking TSC unstable. +Detected 265.275 MHz processor. @@ -102,7 +101,7 @@ -Time: pit clocksource has been installed. +Time: tsc clocksource has been installed. @@ -140,8 +139,9 @@ -Clocksource tsc unstable (delta = -234073763 ns) +Clocksource tsc unstable (delta = -234191628 ns) ata1.00: configured for UDMA/33 +Time: pit clocksource has been installed. So it seems that the blacklisting is not needed anymore, as the unstability is now detected automatically. -- Tero Roponen, <tero.roponen@...il.com> - 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