Bug 88851 - [BISECTED]Intel turbo boost broken after resume from suspend.
Summary: [BISECTED]Intel turbo boost broken after resume from suspend.
Status: CLOSED CODE_FIX
Alias: None
Product: Power Management
Classification: Unclassified
Component: intel_pstate (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Kristen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-24 20:18 UTC by qbanin
Modified: 2015-03-31 20:08 UTC (History)
7 users (show)

See Also:
Kernel Version: 3.17.3+ and 3.18-rc*
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description qbanin 2014-11-24 20:18:01 UTC
Hi,

Since kernel release 3.17.3 and for all 3.18-rc releases Intel turbo boost for my Ivy Bridge cpu doesn't work after resume from suspend. After several test I found out, that reverting commit c034871712730a33e0267095f48b62eae958499c solved my issue.
Comment 1 Len Brown 2014-12-16 00:59:50 UTC
do you modify any of the sysfs parameters related to intel_pstate
before the suspend?

do all p-states fail to work after the resume,
or just states above the base (guaranteed) frequency?
(you can check by running turbostat and watching if the frequency changes
with changes in load)
Comment 2 qbanin 2014-12-16 09:22:55 UTC
My CPU can scale 1200-2400Mhz without turbo and up to 3200 with turbo enabled (for all cores) and it works like this until STR. After resume CPU can still scale 1200-2400 but not higher (TURBO not working).
Comment 3 qbanin 2014-12-16 09:40:47 UTC
I don't modify any intel_pstate related sysfs parameters.
Comment 4 Len Brown 2015-03-24 01:17:46 UTC
is this still a problem when using the latest upstream kernel?
Comment 5 Robin Herink 2015-03-26 00:18:48 UTC
I've noticed this problem too since about 3.18.
My CPU is Intel Sandy Bridge 2500K and just as the OP says. After starting up my computer the CPU scales up to 4200MHz. After resume from sleep it only goes up to 3300MHz. 
Sorry but I can't help with any kernel bisecting. My best is installing the kernel from .deb files.
Comment 6 qbanin 2015-03-27 17:52:09 UTC
Fixed in 3.19.x kernels.
Comment 7 Rafael J. Wysocki 2015-03-31 20:08:10 UTC
Closing then, thanks!

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