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, <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
