Bug 156395 - top shows almost constant CPU usage stats
Summary: top shows almost constant CPU usage stats
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Other (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Mads Martin Joergensen
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-09 11:00 UTC by Stephan Binner
Modified: 2006-03-15 11:41 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Binner 2006-03-09 11:00:56 UTC 
Recently 'top' started to show an almost constant CPU usage stat line, like

Cpu(s):  2.3% us,  1.9% sy,  5.3% ni, 82.1% id,  8.2% wa,  0.1% hi,  0.1% si

even if the machine is busy. I looks like the numbers are now an average of a very long time while they have previously only be over the display update inverval.
Comment 1 Michael Gross 2006-03-09 11:56:49 UTC 
I would plead for the `classic' behaviour and I think many users, too.
Comment 2 Hendrik Vogelsang 2006-03-10 10:56:59 UTC 
we dont change any settings in top. so those are the default settings. Either you live with it or you configure top to behave otherwise...
Comment 3 Stephan Binner 2006-03-10 12:34:31 UTC 
Please give a reference that it actually is a setting / how to change it.

quoting 'man top':

 k: %CPU  --  CPU usage
 The  task's  share of the elapsed CPU time since the last screen update
Comment 4 Stephan Binner 2006-03-10 13:20:51 UTC 
Henne suggested to build procps without procps-3.2.5-cpu_hotplug.patch and so I did and then the reported error is gone.
Comment 5 Dennis Sieben 2006-03-13 16:49:17 UTC 
I would like to say that the bug appears here too. And it's gone after installation of the packages Stephan build without the cpu_hotplug.patch. It seems, that this occurs on every 10.1 beta 7 machine (3 of 3 I've seen so far had the problem).
Comment 6 Hendrik Vogelsang 2006-03-15 11:41:30 UTC 
fixed patch submitted