From: Jim Henderson <hendersj@mindspring.com>
To: J Sloan <jjs@pobox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: kernel BUG at filemap.c:791
Date: Sun, 25 Nov 2001 16:17:47 -0700 [thread overview]
Message-ID: <3C017C1B.8B8610DE@mindspring.com> (raw)
In-Reply-To: <3C016E08.3C2D2537@mindspring.com> <3C017A6E.A4A3E2A6@pobox.com>
J Sloan wrote:
> Wow, it must have taken quite some effort
> to patch a 2.2 kernel for ext3!
>
> OK, assuming you really mean 2.4.14, there
> is a patch floating around the list for that -
You are correct, I fat-fingered the kernel version, 2.4.14 is what I'm
running. Been running 2.4.x kernels for quite a while now, and I catch
myself freqently making that mistake when I type the version.
> I had a compaq 6500 that would scribble
> on the disk and then lock up hard at some
> random point in time - but that behaviour
> could be triggered immediatley by running
> dbench - Look for the compaq patches from
> Jens Axboe or better yet, lose 2.4.14 and go
> straight to 2.4.16-pre1, since it has the ida
> raid fixes, and ext3 support already.
Will give the 2.4.16-pre1 kernel a shot and see how it behaves.
I should have mentioned in my intial post as well that I've seen both
hard locks (as in this case) and soft locks (where I could use the
'magic sysreq key' feature), both of which referenced this particular
code segment.
Thanks for the quick response.
Jim
prev parent reply other threads:[~2001-11-25 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 22:17 PROBLEM: kernel BUG at filemap.c:791 Jim Henderson
2001-11-25 23:10 ` J Sloan
2001-11-25 23:17 ` Jim Henderson [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=3C017C1B.8B8610DE@mindspring.com \
--to=hendersj@mindspring.com \
--cc=jjs@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.