From: Peter Rival <frival@zk3.dec.com>
To: Bob McElrath <mcelrath+linux@draal.physics.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Alpha "process table hang"
Date: Wed, 11 Apr 2001 13:18:01 -0400 [thread overview]
Message-ID: <3AD491C9.6424D932@zk3.dec.com> (raw)
In-Reply-To: <20010411104040.A8773@draal.physics.wisc.edu> <3AD489D1.D5FCCB4B@zk3.dec.com> <20010411120044.A6472@draal.physics.wisc.edu>
Hmpf. Haven't seen this at all on any of the Alphas that I'm running. What
exact system are you seeing this on, and what are you running when it happens?
- Pete
Bob McElrath wrote:
> Peter Rival [frival@zk3.dec.com] wrote:
> > You wouldn't happen to have khttpd loaded as a module, would you? I've seen
> > this type of problem caused by that before...
>
> Nope...
>
> >
> > - Pete
> >
> > Bob McElrath wrote:
> >
> > > I've been experiencing a particular kind of hang for many versions
> > > (since 2.3.99 days, recently seen with 2.4.1, 2.4.2, and 2.4.2-ac4) on
> > > the alpha architecture. The symptom is that any program that tries to
> > > access the process table will hang. (ps, w, top) The hang will go away
> > > by itself after ~10minutes - 1 hour or so. When it hangs I run ps and
> > > see that it gets halfway through the process list and hangs. The
> > > process that comes next in the list (after hang goes away) almost always
> > > has nonsensical memory numbers, like multi-gigabyte SIZE.
> > >
> > > Linux draal.physics.wisc.edu 2.3.99-pre5 #8 Sun Apr 23 16:21:48 CDT 2000
> > > alpha unknown
> > >
> > > Gnu C 2.96
> > > Gnu make 3.78.1
> > > binutils 2.10.0.18
> > > util-linux 2.11a
> > > modutils 2.4.5
> > > e2fsprogs 1.18
> > > PPP 2.3.11
> > > Linux C Library 2.2.1
> > > Dynamic linker (ldd) 2.2.1
> > > Procps 2.0.7
> > > Net-tools 1.54
> > > Kbd 0.94
> > > Sh-utils 2.0
> > > Modules Loaded nfsd lockd sunrpc af_packet msdos fat pas2 sound
> > > soundcore
> > >
> > > Has anyone else seen this? Is there a fix?
> > >
> > > -- Bob
> > >
> > > Bob McElrath (rsmcelrath@students.wisc.edu)
> > > Univ. of Wisconsin at Madison, Department of Physics
> > >
> > > ------------------------------------------------------------------------
> > > Part 1.2Type: application/pgp-signature
> -- Bob
>
> Bob McElrath (rsmcelrath@students.wisc.edu)
> Univ. of Wisconsin at Madison, Department of Physics
>
> ------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
next prev parent reply other threads:[~2001-04-11 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 15:40 Alpha "process table hang" Bob McElrath
2001-04-11 16:44 ` Peter Rival
2001-04-11 17:00 ` Bob McElrath
2001-04-11 17:18 ` Peter Rival [this message]
2001-04-11 17:57 ` Bob McElrath
[not found] ` <E14nOzo-0007Ew-00@the-village.bc.nu>
2001-04-13 13:48 ` Bob McElrath
2001-04-17 15:07 ` generic rwsem [Re: Alpha "process table hang"] Andrea Arcangeli
2001-04-17 15:28 ` Bob McElrath
2001-04-19 16:21 ` Bob McElrath
2001-04-19 17:17 ` Andrea Arcangeli
2001-04-23 23:27 ` Bob McElrath
2001-04-23 23:40 ` Andrea Arcangeli
2001-04-17 15:45 ` Christoph Hellwig
2001-04-17 16:59 ` David Howells
2001-04-17 17:55 ` Andrea Arcangeli
[not found] ` <200104111642.f3BGg6930131@kanga.hofr.at>
2001-04-11 18:49 ` Alpha "process table hang" Bob McElrath
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=3AD491C9.6424D932@zk3.dec.com \
--to=frival@zk3.dec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcelrath+linux@draal.physics.wisc.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