mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: John Jasen <jjasen1@umbc.edu>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
	Andrew Morton <akpm@zip.com.au>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org
Subject: Re: 2.4.17 RAID-1 EXT3  reliable to hang....
Date: Sun, 20 Jan 2002 21:57:28 +0200	[thread overview]
Message-ID: <20020120215728.B1112@mea-ext.zmailer.org> (raw)
In-Reply-To: <20020120193141.A1112@mea-ext.zmailer.org> <Pine.SGI.4.31L.02.0201201422500.1767115-100000@irix2.gl.umbc.edu>
In-Reply-To: <Pine.SGI.4.31L.02.0201201422500.1767115-100000@irix2.gl.umbc.edu>; from jjasen1@umbc.edu on Sun, Jan 20, 2002 at 02:24:40PM -0500

On Sun, Jan 20, 2002 at 02:24:40PM -0500, John Jasen wrote:
> Really?
>   Software raid?
> I have a quad ppro that is doing ext3/md just fine, and its running
> 2.4.17.

  Indeed. I didn't have problems with dual PPro200, but after I did
  upgrade it to dual P-III-750, it does hang up.  Machines have
  128 MB, and 750 MB memory, respectively.  (Disks and host controller
  were moved over.)

  I recall having ran same earlier PPro optimized 2.4 kernel on PPro200,
  and on P-III (2.4.6-ac1, or 2.4.10).  It hung up too, which prompted 
  research on kernel versions.

  This all does point to some sort of deadlock window somewhere.
  It appears to be practically untriggerable with PPro200, but
  trivial to hit with P-III-750.

  Now to have a reliable way to find where the CPUs are spinning
  when the thing does not work...  (I have tested kdb: keyboard
  dies at hangup -> kdb becomes non-functional...)

> --
> -- John E. Jasen (jjasen1@umbc.edu)
> -- In theory, theory and practise are the same. In practise, they aren't.

/Matti Aarnio

  reply	other threads:[~2002-01-20 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 14:36 Matti Aarnio
2002-01-07  8:00 ` Matti Aarnio
2002-01-07  8:19   ` Andrew Morton
2002-01-07  8:38     ` Matti Aarnio
2002-01-07  8:39     ` Oliver Paukstadt
2002-01-07  8:49       ` Andrew Morton
2002-01-07  9:51       ` Richard Guenther
2002-01-07 10:09         ` Andrew Morton
2002-01-07 10:33           ` Richard Guenther
2002-01-20 17:31           ` Matti Aarnio
2002-01-20 19:24             ` John Jasen
2002-01-20 19:57               ` Matti Aarnio [this message]
2002-01-21  0:22                 ` Oliver Xymoron
2002-01-07 13:45         ` Alan Cox

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=20020120215728.B1112@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=akpm@zip.com.au \
    --cc=jjasen1@umbc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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®