On 12/20/2007 01:32 AM, Carlos E. R. wrote: > 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 According to an error message on my system, I think your clock and "lazy desktop" are the same core problem. From your other posts, it appeared 10.3 introduced processor frequency control to your system. From my system, it says something to the effect, marking tsc as unstable due to cpufreq changes. My CPU does have Cool and Quiet, so it sounds correct. Mine uses therefore acpi_pm. jmorris:/home/joe # cat /sys/devices/system/clocksource/clocksource0/current_clocksource acpi_pm I would therefore suggest to pass cpufreq=no as a boot argument, and use tsc, to see if that allows your clock to work correctly, without a cpu frequency change perhaps causing a "lazy desktop" spell. > > * 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. Ouch. Sorry. I based that on what a few others wrote in. I had no idea it would cause such problems on your system. > > * pit I haven't tried. Should I? > After what jiffies did, I wouldn't. Is this your system with xfs? Just trying not to offer bad advice.
-- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
