Bug 56753
Summary: | ps is hung, forever | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Frank Hirtz <fhirtz> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
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: | 2003-03-26 18:39:53 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
Frank Hirtz
2001-11-26 23:02:22 UTC
There's a known deadlock opportunity in the coredump code vs a semaphore "ps" or "top" take. Is it possible the task in question was about to dump core ? I doubt this is the problem, unless the subprocesses spawned by "man lockd" often coredump, especially with nobody else on the system... and neither ps or top were running at the time - I ran ps after the "man" command seemed to hang, not before. which filesystem(s) are in use? esp where are the manpages ? afs (openafs 1.2.2) mounted, like most of the installed and running software in our environment. There were no afs errors on the console or in syslog messages before, during or after the time of the /proc hang. There's no oops in dmesg I assume ? No oops or any interesting messages anywhere. Ok can you enable sysreq and get alt-sysreq-T output ? That should give a list of processes and where in the kernel they are; hopefully that will shed light on where things are stuck. Corrected in 2.4.9-e.8 kernel. |