Bug 1506321 - CPU frequency scaling failing (started with kernel 4.13.5):
Summary: CPU frequency scaling failing (started with kernel 4.13.5):
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-25 17:19 UTC by Flo H.
Modified: 2017-10-25 17:32 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-25 17:32:49 UTC
Type: Bug


Attachments (Terms of Use)

Description Flo H. 2017-10-25 17:19:13 UTC
Description of problem:

Starting with kernel 4.13 my Fedora Workstation with Gnome DE is stuck at one frequency (2.69Ghz), scaling does not happen

Version-Release number of selected component (if applicable):
kernel-core-4.13.5-100.fc25.x86_64
kernel-core-4.13.6-100.fc25.x86_64
kernel-core-4.13.8-100.fc25.x86_64

How reproducible:

100%

Steps to Reproduce:
1.Start machine with one of the affected kernels 
2.monitor CPU frequency
3.

Actual results:
Freq. remains constant, independent of demand


Expected results:
CPU scaling

Additional info:
better report it to upstream?

Comment 1 Flo H. 2017-10-25 17:21:00 UTC
Maybe good to know what CPU this happens on:

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 69
Model name:            Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
Stepping:              1
CPU MHz:               1061.938
CPU max MHz:           3300.0000
CPU min MHz:           800.0000
BogoMIPS:              5387.54
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              4096K
NUMA node0 CPU(s):     0-3
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 pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts

Comment 2 Flo H. 2017-10-25 17:32:49 UTC
sorry, for the mess. The CPU is actually scaling - I just didn't realize the that it is only the CPU Power Manager extension that is acting up. Sorry for the confusion once again!


Note You need to log in before you can comment on or make changes to this bug.