-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-12-16 at 16:28 -0800, Linda Walsh wrote:
Good idea... but it doesn't appear to be that easy.
Never is :-(.
It would likely be at the kernel level - like the kernel is going into a "low-load" setting -- since your system isn't suspending or going to sleep. There are some cpu scheduling modules in the kernel (util 'powertop' makes suggestions for modules to include for laptop or low power systems. Something the "cpufreq_ondemand" module in the in a suse stock kernel (2.6.18.2-34) I see cpufreq modules for conservative, ondemand, powersave.
In some kernel version (gee, am just so specific -- I read information in greater amounts than my brain auto-indexes... (:-))
Doesn't happen to us all? :-)
I thought there was a bug in some later kernel version concerning the new tickless kernel and the ondemand-cpu module, but I don't think the tickless patches are in 2.6.18.
tickless... sounds familiar.
I wonder if there are any ways to tweak those modules -- but it appears they would only be used on a system that has a variable cpu frequency -- so unless you have that hardware....(what hw did you say you had?)...
I'm not sure if my hardware has that capacity. It is a pentium IV @ 1800, single cpu. Lets see what /proc says: nimrodel:~/notas # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 1 model name : Intel(R) Pentium(R) 4 CPU 1.80GHz stepping : 2 cpu MHz : 1800.190 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm bogomips : 3603.26 clflush size : 64 Then, in /proc/acpi/processor/CPU0/* info: processor id: 0 acpi id: 1 bus mastering control: no power management: yes throttling control: yes limit interface: yes limit: active limit: P0:T0 user limit: P0:T0 thermal limit: P0:T0 power: active state: C2 max_cstate: C8 bus master activity: fb7ef96b maximum allowed latency: 6666 usec states: C1: type[C1] promotion[C2] demotion[--] latency[000] usage[16988520] duration[00000000000000000000] *C2: type[C2] promotion[--] demotion[C1] latency[090] usage[42284950] duration[00000000738930421870] throttling: state count: 2 active state: T0 states: *T0: 00% T1: 50% My suspect is the clock. I was having problems with the default system clock, which is 'acpi_pm', which had delays of several minutes per hour. I changed to 'tsc', which works, although the kernel complains during boot: nimrodel:~ # grep -i "clock\|tsc\|TSC" /var/log/boot.msg <6>Time: tsc clocksource has been installed. <6>Real Time Clock Driver v1.12ac <4>Marking TSC unstable due to: possible TSC halt in C2. <=== <6>Time: acpi_pm clocksource has been installed. <6>intel8x0_measure_ac97_clock: measured 50881 usecs <6>intel8x0: clocking to 48000 doneSetting up the hardware clockdone And: Dec 8 13:56:52 nimrodel kernel: Clocksource tsc unstable (delta = 32800377181 ns) However, I think I had instances of these freezing episodes weeks ago, before I set the 'tsc' clock, so... I have no idea. Another symptom: Twice, completely randomly, the system froze. The last time was several days ago. The keyboard stopped responding, the mouse, the display... I thought of powering another machine and entering through ssh; but the moment the other machine had finished booting up, my main machine continued working as if nothing had happened. This has happened twice, and it is very weird. The only thing I know for sure is that it is a software issue of suse 10.3: they started the day after I upgraded. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHZc4vtTMYHG2NR9URAonwAJ4gAlNIHos4nyPHbHoIshnzmAC9swCgiFMH dq+aqxLD/qrkqBmEhyAJjuE= =SkAc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org