Bug 132130
| Summary: | ps command hang. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Jaechul Yoo <yoojchul> |
| Component: | kernel | Assignee: | Jason Baron <jbaron> |
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | CC: | knoel, riel, shillman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | ia64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-01-18 16:52:03 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: | |||
This looks like something for which you would be best off going through support. Please call 800-REDHAT1, or go to https://www.redhat.com/apps/support/ This is clearly a kernel problem. Reading the /proc/*/stat files should never hang; there is nothing ps can do to handle this problem. Jaechul, next time the problem occurs, could you please: 1) send us the output of sysrq-t 2) send us the output of /sbin/lsmod thank you, Rik As there has been no additional information in this bug for 4 months, I'm closing this. If there is new information as requested in comment #3, feel free to reopen and include the new information. |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: ps command hang. The same problem as bugzilla 46937 occurs at HP rx4640(IA64) with Redhat AS 2.1(Up date2), 2.4.18-e.31. It isn't easy to reproduce the problem. I have only output of strace. stat("/proc/4410", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 open("/proc/4410/stat", O_RDONLY) = 7 read(7, Version-Release number of selected component (if applicable): How reproducible: Couldn't Reproduce Steps to Reproduce: 1.not easy to reproduce the problem 2. 3. Additional info: Unfornately customer executes the command much to monitor theirs applications.