-----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.
I just tried, and my system crashed:
echo jiffies > /sys/devices/system/clocksource/clocksource0/current_clocksource
I tried again, in runlevel 3, and I discovered that the clock stopped. I
tried again to go back to tsc, but the clock continued stopped. I tried to
reboot, and reboot crashed.
Is no good.
* acpi_pm looses time, like several minutes per hour.
* tsc "appears" to work well, but might be suspicious
* jiffies doesn't even work, time stops, applications depending on the clock
stop - even "halt" stops when issuing a beep because the beep never times
out.
* pit I haven't tried. Should I?
:-/
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFHaVXPtTMYHG2NR9URAvzNAJ9acZlnuG3Q01zbzJbc8HcXsGW15ACgiiYt
wsXucVfkphxbySqm4FgaQFY=
=VMjg
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
