Turbo mode on i7 is not enabled upon resume

Bug #1452460 reported by Jasper
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Turbo mode is not enabled upon resume from suspend.

To enable I must issue:

``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo``

I would expect that Turbo was re-enabled by default from resume.

I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above commands, but clearly that mechanism is depreciated.

I am reporting this bug against systemd as I assume that it is managing the running of startup and resume scripts.

A quick hack solution would be appreciated in the short term.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu4
Uname: Linux 4.0.0-040000rc7-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 7 09:11:12 2015
InstallationDate: Installed on 2015-04-14 (22 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: Acer Aspire S7-392
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-040000rc7-generic root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.12
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Storm2
dmi.board.vendor: Acer
dmi.board.version: V2.12
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.12
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12:
dmi.product.name: Aspire S7-392
dmi.product.version: V2.12
dmi.sys.vendor: Acer

Revision history for this message
Jasper (jasper-mackenzie) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

That should be done by the kernel itself. In the meantime you can put a script into /lib/systemd/system-sleep/, they work much like the old pm-utils/sleep.d/ scripts. See "man systemd-sleep" for details.

affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jasper (jasper-mackenzie) wrote :

Many thanks for the quick response. I will disseminate this to the many questions in ask-ubuntu relating to resume scripts.

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jasper, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

tags: added: latest-bios-2.12
removed: turbo
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Jasper (jasper-mackenzie) wrote :

Using linus' latest kernel from git (12 hours old) the `problem' persists, and turbo must be re-enabed manually or via systemd script.
I built the deb-pkg target.
I will test the other ubuntu versions soon.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-rc2
Revision history for this message
penalvch (penalvch) wrote :

Jasper, could you please test the latest mainline kernel 4.1-rc2 (not a daily pulled from git) and then advise to the results?

Revision history for this message
Jasper (jasper-mackenzie) wrote :

The `problem' is fixed in 4.1-rc2.
 But
As with the `echo 0... echo 1`... method the processor is _always_ in turbo once it has resumed from sleep.
On my i7-4500U this is about 2.78 and 2.97Ghz.

tags: added: kernel-bug-fixed-upstream-4.1-rc2
removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-rc2
Revision history for this message
penalvch (penalvch) wrote :

Jasper, just to clarify, in 4.1-rc2 do you have to use your WORKAROUND to enable turbo mode after resuming from suspend, or is it automatically enabled?

Revision history for this message
Jasper (jasper-mackenzie) wrote :

I do not use the workaround, and turbo mode is automatically enabled.

penalvch (penalvch)
tags: added: kernel-bug-fixed-upstream needs-reverse-bisect
Revision history for this message
Jasper (jasper-mackenzie) wrote :

Sorry Christopher,
 Further testing reveals that the bug is still present in 4.1-rc2. No idea why it worked the first time, but it has not subsequently.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-rc2
removed: kernel-bug-fixed-upstream kernel-bug-fixed-upstream-4.1-rc2 needs-reverse-bisect
Revision history for this message
penalvch (penalvch) wrote :

Jasper, did this issue not occur in a release prior to Vivid?

Revision history for this message
Jasper (jasper-mackenzie) wrote : Re: [Bug 1452460] Re: Turbo mode on i7 is not enabled upon resume

I have never used this machine with anything less than 15.04, so sorry I
cannot say.

On 10 May 2015 at 12:13, Christopher M. Penalver <
<email address hidden>> wrote:

> Jasper, did this issue not occur in a release prior to Vivid?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1452460
>
> Title:
> Turbo mode on i7 is not enabled upon resume
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> Turbo mode is not enabled upon resume from suspend.
>
> To enable I must issue:
>
> ``echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
> echo 1 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
> echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo``
>
> I would expect that Turbo was re-enabled by default from resume.
>
> I created a script in /usr/lib/pm-utils/sleep.d/ to issue the above
> commands, but clearly that mechanism is depreciated.
>
> I am reporting this bug against systemd as I assume that it is
> managing the running of startup and resume scripts.
>
> A quick hack solution would be appreciated in the short term.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: systemd 219-7ubuntu4
> Uname: Linux 4.0.0-040000rc7-generic x86_64
> ApportVersion: 2.17.2-0ubuntu1
> Architecture: amd64
> CurrentDesktop: Unity
> Date: Thu May 7 09:11:12 2015
> InstallationDate: Installed on 2015-04-14 (22 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
> MachineType: Acer Aspire S7-392
> ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-040000rc7-generic
> root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@
> noprompt persistent quiet splash vt.handoff=7
> SourcePackage: systemd
> UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 05/20/2014
> dmi.bios.vendor: Insyde Corp.
> dmi.bios.version: V2.12
> dmi.board.asset.tag: No Asset Tag
> dmi.board.name: Storm2
> dmi.board.vendor: Acer
> dmi.board.version: V2.12
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: Acer
> dmi.chassis.version: V2.12
> dmi.modalias:
> dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12:
> dmi.product.name: Aspire S7-392
> dmi.product.version: V2.12
> dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452460/+subscriptions
>

Revision history for this message
penalvch (penalvch) wrote :

Jasper, for regression testing purposes, could you please test http://old-releases.ubuntu.com/releases/14.04.0/ubuntu-14.04-desktop-amd64.iso and advise to the results?

Revision history for this message
Doug Smythies (dsmythies) wrote :

see also: https://bugzilla.kernel.org/show_bug.cgi?id=90421
particularly the entries from Marien.

This issue does not manifest the same for all i7 processors.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.