public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@linux.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.4.0-release (and a few priors) stalls
Date: Thu, 04 Jan 2001 01:58:37 -0800	[thread overview]
Message-ID: <3A54494D.C7DA0455@linux.com> (raw)

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

Recently, about test 12 I believe, I started experiencing stalls.
I believe it has to do with VM pressure but I'm not sure.

What happens:  5-60 second instant dead stall, nothing at all happens.
No sound/key/disk/anything activity, screen updates stop in the middle
of an update.  Until recently I was mistaking this as a lockup and
rebooting (thank you reiserfs).  Now I just wait it out.  I'm away for
holiday/vacation so I can't hookup kbd. :(

Environment: normally swap is full -but- buffers can have any amount of
free listed, sometimes well over 100 megs.

After the stall resumes, everything starts right up and sings along
fine.  There aren't any kernel messages indicating something was funny.

This is different from running out of normal pages, the system starts to
thrash and slows considerably, almost unusable, but over a period of
10-20 seconds.  If I add swap quickly, X won't get killed.
(unfortunately, X seems to get killed 9/10 times because netscape took
too long to die so the kernel kept killing).

-d


[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 274 bytes --]

begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;;;;;
version:2.1
email;internet:david@blue-labs.org
title:Blue Labs Developer
note;quoted-printable:GPG key: http://www.blue-labs.org/david@nifty.key=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard

             reply	other threads:[~2001-01-04  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04  9:58 David Ford [this message]
2001-01-04 14:09 ` 2.4.0-release (and a few priors) stalls Rik van Riel

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=3A54494D.C7DA0455@linux.com \
    --to=david@linux.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