Bug 523612
| Summary: | Top reports impossible CPU percentage | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Konstantin Svist <fry.kun> | ||||
| Component: | procps | Assignee: | Jaromír Cápík <jcapik> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | ovasik, rvokal | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-27 14:23:14 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*ping* is this a normal condition? hello Konstantin, Thanks for the report. This condition is probably a bug in top, I will investigate it. hello, the cause of this may be a variable overflow I have built a test package for Fedora 11 (you have the bug reported for this release, so I assume this is the version you use) can you please test, if the problem disappears? http://koji.fedoraproject.org/koji/taskinfo?taskID=2077071 F12 version of the test package: http://koji.fedoraproject.org/koji/taskinfo?taskID=2077142 I have not seen this problem lately, it's probably fixed. I'll let you know if I see it again OK, I will close this CURRENTRELEASE now, feel free to reopen if it appears again Just saw this on procps 3.2.8-3.fc12 Wanted to update to your test version but looks like it's gone now.. and I don't see it in updates-testing. Any idea when it'll be pushed? hello, I only made a scratch build with a custom patch, but unfortunately I lost the patch when I updated some directories and forgot where the problem was... moving this back to "assigned" and next time I'll discover this again I will attach the patch to the bug - I didn't know scratch builds have such short lifespan :( moving bug back to assigned and let's see if I find it again This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping guess let's switch it to 12 so the bug won't get closed :) This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. FYI: this seems to happen a lot when the process is killed/dying Any updates? It's still happening This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 361200 [details] copy of top output Description of problem: On a loaded system, top sometimes briefly reports one process as taking up 9999.0% CPU Version-Release number of selected component (if applicable): procps version 3.2.7 How reproducible: on a well loaded system, the bug shows up about every 30 seconds Additional info: The computer in question has 2 4-core CPUs, so 800% should be the theoretical maximum reported CPU usage for any process