CPU frequency stuck at minimum value
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
koba | ||
thermald (Ubuntu) |
Incomplete
|
High
|
koba |
Bug Description
I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks.
I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor.
Here is the output of some experiments I ran while Phoronix's c-ray test was running.
______________
gjditchf@
cpu MHz : 400.008
cpu MHz : 400.002
cpu MHz : 400.002
cpu MHz : 400.003
cpu MHz : 400.005
cpu MHz : 400.003
cpu MHz : 400.001
cpu MHz : 400.004
gjditchf@
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: 400 MHz - 4.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 1.60 GHz.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
gjditchf@
Setting cpu: 0
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 4 12:57:25 2018
InstallationDate: Installed on 2018-04-28 (6 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CurrentDesktop: KDE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-28 (10 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp.
Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Spectre Laptop 13-af0xx
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/13/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.06
dmi.board.
dmi.board.name: 83A2
dmi.board.vendor: HP
dmi.board.version: 55.24
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre Laptop 13-af0xx
dmi.product.
dmi.sys.vendor: HP
tags: | added: cscc |
Changed in linux (Ubuntu): | |
assignee: | Colin Ian King (colin-king) → Ubuntu Kernel Team (ubuntu-kernel-team) |
Changed in thermald (Ubuntu): | |
assignee: | Colin Ian King (colin-king) → Ubuntu Kernel Team (ubuntu-kernel-team) |
Changed in linux (Ubuntu): | |
assignee: | Ubuntu Kernel Team (ubuntu-kernel-team) → koba (kobako) |
Changed in thermald (Ubuntu): | |
assignee: | Ubuntu Kernel Team (ubuntu-kernel-team) → koba (kobako) |
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the latest v4.17 kernel[0].
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
[0] http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v4.17-rc4