Bug 75117 - (FS PROC)System idle time in /proc/stat does not match CPU idle time
Summary: (FS PROC)System idle time in /proc/stat does not match CPU idle time
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-04 16:54 UTC by Lev Makhlis
Modified: 2008-08-01 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:40:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Lev Makhlis 2002-10-04 16:54:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.0.0-10; Linux)

Description of problem:
The idle time in the "cpu" line (which is supposed to be the sum of all individual CPUs) often differs by 10-20 ms (i.e., 1-2 userspace ticks) from the idle time in the "cpu0" line on a single-processor system.

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


How reproducible:
Sometimes

Steps to Reproduce:
1. grep cpu /proc/stat

 

Actual Results:  cpu  513891 3024 68072 12500724
cpu0 513891 3024 68072 12500722


Expected Results:  Identical numbers

Additional info:

This is a round-off problem.  When the total idle time is calculated,
the hz_to_std() conversion is applied to user, nice and system times
separately, while for an individual CPU, the conversion is applied to the sum.

Comment 1 Bugzilla owner 2004-09-30 15:40:00 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



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