public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Huey (Hui) <billh@gnuppy.monkey.org>
To: Greg Fitzgerald <gregf@closeedge.net>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, adilger@clusterfs.com
Subject: Re: ext3 journal/IDE problems ?
Date: Fri, 9 Aug 2002 21:19:41 -0700	[thread overview]
Message-ID: <20020810041941.GA4192@gnuppy.monkey.org> (raw)
In-Reply-To: <20020809110938.24de8a00.gregf@closeedge.net>

On Fri, Aug 09, 2002 at 11:09:38AM -0400, Greg Fitzgerald wrote:
> I have been having problems with ext3 hardlocking while in X and in
> Console. Symptom one is while in console moving large ammounts of data
> around between partions it will hardlock. Symptom two is sometimes I
> will leave my computer for a few minutes (on a very rar occasion :P )
> when i return x is hardlocked. Was running XFS and Resierfs before I
> tried ext3 and never had these problems. Any information I can provide
> let me know.

I use to get those hard locks, but I wasn't sure if was my hardware or
the kernel using preempt. After using 2.5.30 for a while, those lock ups
went away, but the progression to this bug happen first with a scheduler
crash in the TCP/IP stack being triggered and then after that application of
Mingo's patch (from a previous email) that fixed the crashes, it started
to trigger ext3 assertions.

It's a very strange bug. Not sure what to say about it.

bill


      reply	other threads:[~2002-08-10  4:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09  4:04 ext3 journal/IDE problems ? Bill Huey
2002-08-09  6:37 ` Andreas Dilger
2002-08-09  9:34   ` ext3 journal/IDE problems ? (softirq + sched assert ?) Bill Huey
2002-08-09 15:09 ` ext3 journal/IDE problems ? Greg Fitzgerald
2002-08-10  4:19   ` Bill Huey [this message]

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=20020810041941.GA4192@gnuppy.monkey.org \
    --to=billh@gnuppy.monkey.org \
    --cc=adilger@clusterfs.com \
    --cc=gregf@closeedge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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