Bug 743212 - Something is using 100% CPU and constant IO but TOP does not show it.
Summary: Something is using 100% CPU and constant IO but TOP does not show it.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-04 09:13 UTC by jeff
Modified: 2011-10-10 14:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-10 14:18:46 UTC
Type: ---


Attachments (Terms of Use)
Top Screen Shot showing 100 CPU but process running do not add up to 100? (47.21 KB, image/png)
2011-10-04 09:13 UTC, jeff
no flags Details
Better screen shot (1.06 MB, image/png)
2011-10-04 09:27 UTC, jeff
no flags Details

Description jeff 2011-10-04 09:13:54 UTC
Created attachment 526204 [details]
Top Screen Shot showing 100 CPU but process running do not add up to 100?

Description of problem:
Something is using 100% CPU and constant IO but TOP does not show it.

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

How reproducible:
Always

Steps to Reproduce:
1.Boot up Fedora 15 as a Virtual Box Guest(4.0.12)
2.Log In as a user KDE plasma
3.Run top.
  
Actual results:
100% CPU and all this IO wait. But top is no where near 100%

Expected results:
Idle cpu no IO wait like in Fedora 14

Additional info:See attached screen shot

Comment 1 jeff 2011-10-04 09:27:45 UTC
Created attachment 526210 [details]
Better screen shot

Comment 2 Dave Jones 2011-10-04 15:33:50 UTC
try iotop ?

Comment 3 jeff 2011-10-06 02:45:36 UTC
Will do the next time it happens.

Also, I did perhaps catch the culprit yesterday with TOP it appears VBox client 4.0.12 has an issue.

New version out today 4.1.4 and have installed it and will monitor.

Comment 4 Josh Boyer 2011-10-10 14:18:46 UTC
We're going to close this out for now.  If you can recreate this on a stock Fedora kernel and can gather more data, please reopen.


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