Wow. I've never seen this before. My scaling_min_freq and scaling_max_freq are now set to... 0!
root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# ls -1 * affected_cpus cpuinfo_cur_freq cpuinfo_max_freq cpuinfo_min_freq cpuinfo_transition_latency related_cpus scaling_available_governors scaling_cur_freq scaling_driver scaling_governor scaling_max_freq scaling_min_freq scaling_setspeed root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat * 0 1737414 3700000 1600000 4294967295 0 performance powersave 1737414 intel_pstate performance 0 0 <unsupported> root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# uname -a Linux ossy 4.10.0-041000rc6-generic #201701291830 SMP Sun Jan 29 23:32:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux And now scaling_max_freq is stuck: root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat cpuinfo_max_freq > scaling_max_freq root@ossy:/sys/devices/system/cpu/cpu0/cpufreq# cat scaling_max_freq 0 Inside of the intel_pstate folder, I can move max_perf_pct up to 44 max, and turn on turbo: root@ossy:/sys/devices/system/cpu/intel_pstate# ls -1 max_perf_pct min_perf_pct no_turbo num_pstates turbo_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat * 0 0 1 22 19 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 40 > min_perf_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat min_perf_pct 0 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 100 > max_perf_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat max_perf_pct 44 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 0 > no_turbo root@ossy:/sys/devices/system/cpu/intel_pstate# cat no_turbo 0 root@ossy:/sys/devices/system/cpu/intel_pstate# echo 100 > max_perf_pct root@ossy:/sys/devices/system/cpu/intel_pstate# cat max_perf_pct 44 But I'm sure at some point later it will go down again and not go back up until I change things manually (or reboot). Not entirely sure when this happened. I had it running for over 12 hours (including a lot of load with BOINC projects overnight). It wasn't stuck like this in the morning, but at some point today it got into this state. Nothing strange I can see in my system log, except for maybe [13347.141990] powercap intel-rapl:0: package locked by BIOS, monitoring only But I don't think my BIOS is limiting anything because when I echo 1 > /sys/module/processor/parameters/ignore_ppc it doesn't make a difference, I still can't change any of the values (scaling_max_freq or max_perf_pct) that I want to get my original speed back, only rebooting helps. Anyway, if you don't think this is the right bug I can open another one or something, but unless you can suggest a patch to try or a setting to change I am probably just going to disable pstate on the GRUB command line and be done with it (and of course ensure thermald and powerclamp are running and my fans are in good shape and as dust-free as can be). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1188647 Title: Please change intel_pstate default to disable Status in linux package in Ubuntu: Fix Released Bug description: 3.9 introduced a new default governor on SandyBridge CPUs called INTEL_PSTATE which, when built in and enabled (the default), removes all other governors (like our usual default, ondemand). 3.10 extended this to Ivybridge generation CPUs. In theory, this isn't an awful thing, as the new Intel pstate governor should be higher performance and give better power savings. In theory. In practice, it drives my CPUs to max frequency nearly constantly, spins my fans like mad and, somehow, does all of this while also eating enough CPU time in kernel threads to make my machine choppy, unresponsive, and unable to do simple things like play videos when I get off work. Therefore, I propose that we, for now, toggle intel_pstate to disable by default (I am using intel_pstate=disable on my command line right now, with great success), so it's still built in, and people can play with it, but it's off by default. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: adconrad 2574 F.... pulseaudio CurrentDmesg: [ 30.633035] init: plymouth-stop pre-start process (2079) terminated with status 1 [ 36.086916] br0: port 1(eth0) entered forwarding state Date: Fri Jun 7 08:48:56 2013 HibernationDevice: RESUME=UUID=73040efa-baec-458a-8307-3bca07b26c3c InstallationDate: Installed on 2012-12-09 (179 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121209) MachineType: LENOVO 4173LPB MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic root=UUID=2222aad5-ef31-4428-973f-71740fc7cb6a ro intel_pstate=disable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.9.0-4-generic N/A linux-backports-modules-3.9.0-4-generic N/A linux-firmware 1.109 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8CET55WW (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 4173LPB dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8CET55WW(1.35):bd09/13/2012:svnLENOVO:pn4173LPB:pvrThinkPadT420s:rvnLENOVO:rn4173LPB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4173LPB dmi.product.version: ThinkPad T420s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
