public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: David <david@blue-labs.org>,
	He-Who-Is-Not-Subscribed-to-LKML
	<acapnotic@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.1] system goes glacial, Reiser on /usr doesn't sync
Date: Tue, 20 Feb 2001 11:25:59 -0500	[thread overview]
Message-ID: <1772480000.982686359@tiny> (raw)
In-Reply-To: <3A92560D.2040304@blue-labs.org>



On Tuesday, February 20, 2001 03:33:33 AM -0800 David <david@blue-labs.org>
wrote:

> Kevin Turner wrote:
> 
>> Version:
>> Linux version 2.4.1-pre12 (gcc version 2.95.3 20010125 (prerelease))
>> 
>> Possible suspect players: 
>>   dpkg seems to trigger the bug
>>   ReiserFS is the partition that doesn't sync
>>   binfmt_misc shows up in the call traces.
>> 
>> Symptoms:
>> 
>> The system assumes glacial speeds.  If you're *lucky*, you'll see one
>> widget re-paint in X before the next ice age.  Ctrl-alt-delete is
>> unresponsive, as are attempts to start proccesses via the network or
>> joystick port.  Keypresses to programs such as getty are not echoed.
>> All program output to console and network is stopped dead.  If you leave
>> for a several-hour-long coffee break and come back to it, there's still
>> no evidence that you banged on the keyboard.
> 
> 
> Wild shot in the dark....I'd lay odds that you had about 6-7 Megs free in
> your buffers/cache line, yes?
> 

David, have any of Rik's patches helped here?

-chris


  parent reply	other threads:[~2001-02-20 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010220011536.A10778@troglodyte.menefee>
2001-02-20 10:16 ` [2.4.1] system goes glacial, Reiser on /usr doesn't sync Kevin Turner
2001-02-20 10:30   ` Keith Owens
2001-02-20 11:33   ` David
2001-02-20 12:24     ` Kevin Turner
2001-02-20 16:25     ` Chris Mason [this message]
2001-02-20 12:34   ` Kevin Turner
2001-02-23 23:35   ` Dwayne C. Litzenberger
2001-02-24  2:21     ` Dwayne C. Litzenberger

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=1772480000.982686359@tiny \
    --to=mason@suse.com \
    --cc=acapnotic@users.sourceforge.net \
    --cc=david@blue-labs.org \
    --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