-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Tuesday 2007-12-18 at 07:27 +0800, Joe Morris (NTM) wrote:
But I refuse to believe it can be a hardware problem, because 10.2 had
no problems, and the problems started as soon as I upgraded to 10.3
Maybe it is not indicating a hardware failure, but the source of the
problem. It sounds like it is related to your clock problem. Perhaps
tsc is often marked as unreliable for a reason. Maybe try jiffies,
since the acpi_pm seemed to cause your clock even more problems.
The "acpi_pm" is what the kernel chooses, but doesn't work well. Yep, I
could try "jiffies", I guess... It will take days to make sure if it
helps.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFHZyL0tTMYHG2NR9URAnF9AJ9D5vwseoeKXDZQrKB4gWnU7o4X8QCfYT+9
1is50ZEqq2+udBeeCwoGenA=
=VxbD
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
