Bug 73121
Summary: | top -i fails to display processes & their cpu times correctly | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Joe Korty <joe.korty> |
Component: | procps | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-02-11 13:04:06 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: |
Description
Joe Korty
2002-08-30 22:32:22 UTC
I booted a stock 2.4.18 kernel from ftp.kernel.org on Limbo(NULL); the problem persists. The same stock 2.4.18 kernel booted on a RedHat 7.2 system performed flawlessly. Hence it appears the bug has nothing to do with the kernel itself but with top, with the libraries it calls, or with the new gcc 3.2 compiler. When I grab procps-2.0.7.tar.gz from ftp.gnu.org and compile that under Limbo(NULL), top works fine. Therefore there is something wrong with the way this package was compiled and packaged up into an rpm. I built a virgin package, no configuration changes of any kind. The mysterious result of recompiling and everything works might be explained if RedHat did not recompile *every* *single* rpm for Limbo(NULL), but instead passed through some rpms built under Limbo2 .. |