![]() Prior to this, only cdev:9(intel_pstate) was mentioned. Thermald: Set : threshold:96000, temperature:95000, cdev:1(Processor), curr_state:9, max_state:10 Thermald: match zone 3 trip 0 clamp_valid 0 clamp 2147483647 Thermald: Set : threshold:96000, temperature:96000, cdev:1(Processor), curr_state:10, max_state:10 Thermald: cdev index:1 consecutive call, increment exponentially state 11 In my syslog, i see lines similar to the following: thermald: >thd_cdev_set_state index:1 state:1 :3:0:0:2147483647 force:0 ![]() I can set the governer to "performance" with cpufreq-set -c 0 -g performance for each CPU in turn, but the speeds stay locked in the 316 - 357 MHz range.Īnother update: I'm not sure if this has anything to do with the problem, but around the time the slow-down happened, there is a change in behaviour of thermald. If there's no clear cause for this slowing, is there at least some way to set the speeds back to normal short of rebooting each time? cpufreq-info shows all 8 CPUs were set to "powersave". The output is the same as when the laptop was running at a normal speed: the number 8 repeated 8 times. Update: The slow-down has recurred, and i re-ran the rdmsr command. It has also never happened before updating to 18.10. There was no sleep/suspend that caused the slow speeds in my case. The links seem to refer to Dell laptops, and slow speeds after resuming from sleep. If the slow down happens again, i'll see if it changes. Note that this is after rebooting, which seems to be the only way to recover a normal CPU speed. Any thoughts on where to look to configure this properly? Something seems to have changed between 18.04 and 18.10 that causes this over-enthusiastic power management. The highest temperature i can find right now is 78☌, well below where speeds would normally pick back up. These are "Intel(R) Core(TM) i7-3610QM CPU 2.30GHz" CPUs. The governor "powersave" may decide which speed to useĪll 8 CPUs had speeds in the range 344 - 373 MHz. For example, from cpufreq-info: analyzing CPU 7:ĬPUs which run at the same hardware frequency: 7ĬPUs which need to have their frequency coordinated by software: 7Īvailable cpufreq governors: performance, powersaveĬurrent policy: frequency should be within 1.32 GHz and 1.32 GHz. Now, since the update, it switches to a VERY low speed. This happened in the past, but once things cooled down, the speed would switch higher again. I think (not sure) it occurs when the laptop starts running a little hot, and the intel_pstate switches the CPUs to a lower speed. So according to them, the delta N over N itself determines the switching time, where N is the frequency synthesizer's feedback divisor.Since updating to Ubuntu 18.10, CPU power management seems to be having problems. Lee) that the switching time (i.e., settling time) is a function of the percentage change in the feedback division ratio. Two other authors state (Hamid Rategh and Thomas H. By this rule, a reference frequency of 50 kHz has a settling time of 1 millisecond. IIIT-H is making a processor having clock speed higher than i7 processors having 16 cores. Crawford: 50 reference cycles as a rule of thumb. A more general statement has been given by James A. In the 1970s switching speeds ranged from 1 millisecond to 10 microseconds. Such requirements will vary depending on the design of the synthesizer. For a frequency synthesizer, the switching time or more colloquially the switching speed is the amount of time from when the command for the next frequency is requested until the time that the synthesizer's output becomes usable and meets the specified requirements.
0 Comments
Leave a Reply. |