public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: ps hang in 241-pre10
Date: 27 Jan 2001 17:55:04 -0800	[thread overview]
Message-ID: <94vu5o$1c6$1@penguin.transmeta.com> (raw)
In-Reply-To: <3A724FD2.3DEB44C@reptechnic.com.au> <3A7359BB.7BBEE42A@linux.com> <94voof$17j$1@penguin.transmeta.com> <3A737061.F1B914A3@linux.com>

In article <3A737061.F1B914A3@linux.com>, David Ford  <david@linux.com> wrote:
>Unfortunately klogd reads /proc....erg.
>
>So the following is a painstakingly slow hand translation, I'll only print
>the D state entries unless someone asks otherwise.

You seem to be pretty much able to reproduce this at will, right?

I'd really like to see the raw System.map and dmesg output if your
syslogd doesn't do a proper job of getting the symbols interpreted: just
send the things by email, and I'll put something together.  It's too
hard to interpret your half-way decoded thing, and I really want to see
what this xmms thing is doing.. 

>xmms      D CACC5EA8  4116   713    155   715  (NOTLB)    1493   674
>Call Trace: [<c0124966>] [<c012412f>] [<c01242b8>] [<c0144138>] [<c014238e>]
>[<c0131cd0>] [<c01236b2>]
>       [<c01239f2>] [<c01ac5ca>] [<c010d1f6>] [<c0108e7c>] [<c0108d5f>]
>
>c01248e4 T ___wait_on_page
>c0124984 t __lock_page
>
>c01240dc t truncate_list_pages
>c0124268 T truncate_inode_pages
>c01242d4 t writeout_one_page

This is the smoking gun here, I bet, but I'd like to make sure I see the
whole thing. I don't see _why_ we'd have deadlocked on __wait_on_page(),
but I think this is the thread that hangs on to the mm semaphore.

		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/

  reply	other threads:[~2001-01-28  1:55 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 [this message]
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
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='94vu5o$1c6$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