From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: ps hang in 241-pre10
Date: 27 Jan 2001 08:19:42 -0800 [thread overview]
Message-ID: <94useu$etc$1@penguin.transmeta.com> (raw)
In-Reply-To: <3A724FD2.3DEB44C@reptechnic.com.au> <20010126204324.B10046@vitelus.com> <3A72817E.CFCF0D52@pobox.com> <3A7285D4.9409E63A@linux.com>
In article <3A7285D4.9409E63A@linux.com>, David Ford <david@linux.com> wrote:
>I can quickly and easily duplicate it on my notebook by playing music or
>mpegs in xmms. It may take a few minutes but it's guaranteed.
>
>xmms stalls flat on it's face and anything accessing /proc stalls. If I get
>the time to do it, I'll take a gander at it with kdb.
Please, if you see something like this, just do a simple
<Alt+ScrollLock> followed by <Ctrl+ScrollLock> while in text-mode. The
magic keystrokes will give a stack trace of the currently running
process and all processes respectively.
Then, just look in your /var/log/messages, and if you have everything
set up correctly the system should have done the conversion to symbolic
kernel addresses for you - so you can see directly where the different
processes are sleeping.
Sanity-check that your System.map information (and thus the symbolic
conversion) ooks to be ok: the processes that hang should show up in the
trace as being in __down_failed() or something like that. Tha only
reason for a hang with /proc/<pid>/ tends to be that some process would
have deadlocked on it's MM semaphore or is somehow stuck inside it's
critical region on something else.
Finally, try to pinpoint _which_ process it is. Usully most easily done
by simply seeing where it is that the /proc accesses get stuck, with
something simple like
cd /proc
for i in [0-9]*; do
echo $i
cat $i/stat > /dev/null
done
and see what the last pid it printed out was (not that the above
guarantees that you found the thing, because there might be several
things. But it's one more piece to the puzzle).
And send the information to the kernel mailing list, along with anything
else you might think of.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-27 16:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 4:34 ps hang in 241-pre10 John Sheahan
2001-01-27 4:43 ` Aaron Lehmann
2001-01-27 7:03 ` Shawn Starr
2001-01-27 8:06 ` J Sloan
2001-01-27 8:24 ` David Ford
2001-01-27 9:33 ` Shawn Starr
2001-01-27 11:26 ` John Sheahan
2001-01-27 19:15 ` J Sloan
2001-01-27 23:28 ` David Ford
2001-01-28 0:22 ` Linus Torvalds
2001-01-28 0:36 ` Shawn Starr
2001-01-28 0:43 ` David Ford
2001-01-28 1:05 ` David Ford
2001-01-28 1:55 ` Linus Torvalds
2001-01-28 2:20 ` Marcelo Tosatti
2001-01-28 4:37 ` Linus Torvalds
2001-01-28 3:42 ` Marcelo Tosatti
2001-01-28 4:01 ` Marcelo Tosatti
2001-01-28 17:21 ` Linus Torvalds
2001-01-28 6:10 ` Shawn Starr
2001-01-28 1:15 ` David Ford
[not found] ` <fa.ikhc52v.e68327@ifi.uio.no>
2001-01-28 3:46 ` Håvard Kvålen
2001-01-28 8:59 ` James Sutherland
2001-01-29 15:08 ` Zdenek Kabelac
2001-01-28 0:42 ` J Sloan
2001-01-28 0:44 ` Aaron Lehmann
2001-01-28 1:11 ` David Ford
2001-01-28 1:30 ` J Sloan
2001-01-28 1:51 ` Shawn Starr
2001-01-27 21:14 ` Aaron Lehmann
2001-01-27 16:19 ` Linus Torvalds [this message]
2001-01-27 23:42 ` David Ford
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='94useu$etc$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
/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