[Bug 1018770] New: cpu frequency scaling intel_pstate broken
http://bugzilla.opensuse.org/show_bug.cgi?id=1018770 Bug ID: 1018770 Summary: cpu frequency scaling intel_pstate broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: napseis@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: hi, I just realized that on my machine, the cpu speed is always maximum. I'm running a clean install of Leap 42.2 with all updates. cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 4.40 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 4.40 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Model name: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018770 http://bugzilla.opensuse.org/show_bug.cgi?id=1018770#c1 --- Comment #1 from A V <napseis@gmail.com> --- I forgot to say (how to edit bug ??) that it seems to happen to other people, see: https://forums.opensuse.org/showthread.php/521878-CPU-running-with-top-speed... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018770 http://bugzilla.opensuse.org/show_bug.cgi?id=1018770#c11 rudi mat <bismarel@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bismarel@hotmail.com --- Comment #11 from rudi mat <bismarel@hotmail.com> --- HI Same problem here , cpu i5 5200U temp is running hotter when idle , both with or without intel_pstate disabled https://forums.opensuse.org/showthread.php/521878-CPU-running-with-top-speed... replaced with this one and seems to work now : home:Ledest:kernel 4.4.52-1-default https://software.opensuse.org/package/kernel-desktop-base -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018770 http://bugzilla.opensuse.org/show_bug.cgi?id=1018770#c12 Todd Dailey <tdailey@golden.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tdailey@golden.net --- Comment #12 from Todd Dailey <tdailey@golden.net> --- Identical problem. CPU runs at 3800 - 4400 MHz continuously. Intel i7-4790K cpupower frequency-info outputs: " analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 4.40 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 4.37 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes " Adding intel_pstate=disable to kernel command line results in more normal CPU frequency scaling. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1018770 http://bugzilla.opensuse.org/show_bug.cgi?id=1018770#c13 --- Comment #13 from Todd Dailey <tdailey@golden.net> --- Problem remains in 4.4.70-18.9-default -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com