Bug 1122426 - One core goes to 100% after suspend/resume [NEEDINFO]
Summary: One core goes to 100% after suspend/resume
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-23 08:35 UTC by Valent Turkovic
Modified: 2014-12-10 15:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-10 15:01:35 UTC
valent.turkovic: needinfo? (kernel-maint)

Attachments (Terms of Use)
cpu info (3.60 KB, text/plain)
2014-07-23 08:36 UTC, Valent Turkovic 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Valent Turkovic 2014-07-23 08:35:00 UTC 
Description of problem:
After waking up from suspend my laptop eats up the battery and heats up really bad. I have seen than one core is always at 100% even if I close all the apps that were running. 

Version-Release number of selected component (if applicable):


How reproducible:
50%

Steps to Reproduce:
1. suspend
2. resume
3.

Actual results:


Expected results:
Laptop to work withut heating up and lasting very short on bttery.

Additional info:
Laptop is Asus U36S
Comment 1 Valent Turkovic 2014-07-23 08:36:02 UTC 
Created attachment 920163 [details]
cpu info
Comment 2 Valent Turkovic 2014-07-23 08:38:33 UTC 
Is there any more info that I can provide? Some logs?
Is there any new kernel you wish me to test and report back? 

Current kernel I'm running is 3.15.4 but I have seen this for long time, hoped it will be fixed with some update but as it persisted I finally posted this bug report.
Comment 3 Justin M. Forbes 2014-12-10 15:01:35 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Note You need to log in before you can comment on or make changes to this bug.