Bug 150311 - Unnaccounted for high cpu usage while idle
Summary: Unnaccounted for high cpu usage while idle
Status: NEW
Alias: None
Product: Process Management
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: process_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-26 02:04 UTC by Michael Dale Long
Modified: 2016-08-18 14:05 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.6.0-rc1 and later
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Kernel config used to build 4.6.0-rc1 (114.29 KB, application/octet-stream)
2016-07-26 02:04 UTC, Michael Dale Long
Details

Description Michael Dale Long 2016-07-26 02:04:10 UTC
Created attachment 226441 [details]
Kernel config used to build 4.6.0-rc1

Starting with 4.6.0-rc1, my system began having unexplained CPU usage.  Even when the system is completely idle, the first core would show around 50% CPU.  htop did not show any process associated with the activity, kernel or user.  I run a full tickless kernel, which I thought might have been related, but even going back to a normal kernel tick just spreads the mystery usage across different cores, it doesn't go away.  I ran atop to see if short lived processes were at fault, but it didn't detect any.  I confirmed that this does not occur with 4.5.7, so it was introduced somewhere between 4.5.x and 4.6.0-rc1.  It does still occur on 4.7.0.  All this was tested on an untainted kernel built from linux-stable.
Comment 1 Michael Dale Long 2016-07-29 03:15:17 UTC
I spent some time bisecting from v4.5.7 to v4.6-rc1, and it appears that the problem is introduced in this commit:  f872f5400cc01373d8e29d9c7a5296ccfaf4ccf3

At first glance I have no idea why this commit would be the cause of this behavior, but it is clearly observable in a kernel built from that version and not in one built prior to it.
Comment 2 Sergey Morozov 2016-08-14 22:31:21 UTC
I have the same problem
Comment 3 Sergey Morozov 2016-08-17 23:40:32 UTC
In my case, the cause of the problems is enabled by mistake CONFIG_CONTEXT_TRACKING_FORCE option.
Comment 4 Michael Dale Long 2016-08-18 14:05:29 UTC
Apparently I had the same problem.  Disabling that in 4.7.1 fixed the issue.  Thanks for the information!

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