From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Weird problem.
Date: Tue, 26 Feb 2002 13:01:42 -0500 [thread overview]
Message-ID: <200202261801.NAA07515@math.psu.edu> (raw)
I'm looking at a Plan 9 machine where ps(1) keeps hanging; in particular,
it hangs while trying to open one of the status files under /proc/*. (eg,
open("/proc/$somepid/status", OREAD); hangs). Looking at the source code
to devproc.c, I see that one of the first things procopen() does is lock
p->debug once it finds the proctable entry for the process that particular
file is associated with. My guess, based only on vague feeling and nothing
more substantial, is that there exists some sort of deadlock with p->debug.
Is there a way to see what locks a process holds, short of instrumenting
the kernel to do so? I'd hate to simply reboot the machine, since I think
that the error state would be difficult to recreate, and I'd really like
to understand what's going on. Alternatively, if anyone's seen this before
and knows what's up, that'd be great.
- Dan C.
next reply other threads:[~2002-02-26 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 18:01 Dan Cross [this message]
2002-02-26 23:37 Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202261801.NAA07515@math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).