public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lehmann <aaronl@vitelus.com>
To: John Sheahan <john@reptechnic.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ps hang in 241-pre10
Date: Fri, 26 Jan 2001 20:43:24 -0800	[thread overview]
Message-ID: <20010126204324.B10046@vitelus.com> (raw)
In-Reply-To: <3A724FD2.3DEB44C@reptechnic.com.au>
In-Reply-To: <3A724FD2.3DEB44C@reptechnic.com.au>; from john@reptechnic.com.au on Sat, Jan 27, 2001 at 03:34:26PM +1100

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

On Sat, Jan 27, 2001 at 03:34:26PM +1100, John Sheahan wrote:
> Hi
> my box has been running 2.4.1-pre10 for three days.
> This morning I noticed odd behavioue - ps and top wouuld freeze 
> with no output.

I had the same problem with 2.4.1-pre10 and the zerocopy patchset.
I came home one day and xmms was frozen. Attempting to determine
whether it was stuck in an odd state, I ran ps aux. At a certain
point (presumably just when it started trying to print info about the
xmms process), ps froze up too. And any attempts to killall -9 these
processes made the killall freeze!

I'm not sure what made xmms freeze up in the first place. My first
though was a problem in the zerocopy patchset -- most of my mp3s are
played over NFS. However, XMMS was completely idle during the time I
was away from the computer, so I'm not sure what caused it. It seemed
clear, however, that the problem was contagious between processes.

I reverted back to 2.4.0-ac7 and have not had any more problems of this
nature.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-01-27  4:43 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 [this message]
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
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=20010126204324.B10046@vitelus.com \
    --to=aaronl@vitelus.com \
    --cc=john@reptechnic.com.au \
    --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