mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Anthony Campbell <ac@acampbell.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Repeated lockups caused by ext3?
Date: Sat, 2 Feb 2002 00:23:53 +0200	[thread overview]
Message-ID: <20020202002353.N5808@mea-ext.zmailer.org> (raw)
In-Reply-To: <20020201162055.GA1318@debian.local>
In-Reply-To: <20020201162055.GA1318@debian.local>; from ac@acampbell.org.uk on Fri, Feb 01, 2002 at 04:20:55PM +0000

On Fri, Feb 01, 2002 at 04:20:55PM +0000, Anthony Campbell wrote:
> For the past couple of months I have been getting repeated lockups using
> 2.4 kernels; 2.4.17 at present. They always occur when I'm on line and
> downloading, never at other times, and never on kernel 2.2.20. No
> particular process seems to cause it. When it happens, all keys are
> inoperative, the modem stops working, and the hard disk light is
> permanently on.
> 
> They never occur on my laptop, using kernel 2.4.17.
>
> They began to occur at about 2.4.10. I kept attributing them to VM
> issues and fiddled with all sorts of things in the BIOS, without
> result.
> 
> However, I've now found that they don't occur if I don't use ext3. This
> therefore seems to be the answer in my case. Is this a known issue, and
> is there any way of getting ext3 to work?
> 
> For the record: Processor is Intel Coppermine 600Mhz; 192M memory.
> Not using hdparm.

  Oh dear..  uniprocessor ?
  I get SMP machine to hang when writing 1+ GB file to EXT3 on RAID-1, and 
  having more than 512 MB memory...

> Anthony
> -- 
> Anthony Campbell - running Linux GNU/Debian (Windows-free zone)
> For an electronic book (The Assassins of Alamut), skeptical 
> essays, and over 150 book reviews, go to: http://www.acampbell.org.uk/

/Matti Aarnio

  reply	other threads:[~2002-02-01 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 16:20 Anthony Campbell
2002-02-01 22:23 ` Matti Aarnio [this message]
2002-02-02 19:16   ` Anthony Campbell

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=20020202002353.N5808@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=ac@acampbell.org.uk \
    --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

all inboxes | Powered by JetHome®