From: Andrew Morton <akpm@zip.com.au>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG in ext3 (2.4.18pre1)
Date: Thu, 18 Apr 2002 15:39:15 -0700 [thread overview]
Message-ID: <3CBF4B13.38B20491@zip.com.au> (raw)
In-Reply-To: <5.1.0.14.0.20020418230637.0164d828@mailhost.ivimey.org>
Ruth Ivimey-Cook wrote:
>
> ...
> Apr 17 23:20:01 gatemaster kernel: Assertion failure in
> __journal_file_buffer() at transaction.c:1935: "jh->b_jlist < 9"
> Apr 17 23:20:01 gatemaster kernel: kernel BUG at transaction.c:1935!
That's the first time this has been reported. Conceivably,
ext3 has corrupted the journal_head. More conceivably, some
other part of the kernel scribbled on it. Most conceivably,
your memory flipped a bit.
Best I can suggest is that you give the machine an overnight
run with memtest86.
-
next prev parent reply other threads:[~2002-04-18 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 22:13 Kernel BUG in ext3 (2.4.18pre1) Ruth Ivimey-Cook
2002-04-18 22:39 ` Andrew Morton [this message]
2002-04-19 19:51 ` Ruth Ivimey-Cook
2002-04-19 1:34 ` Greg KH
2002-04-19 8:43 ` kwijibo
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=3CBF4B13.38B20491@zip.com.au \
--to=akpm@zip.com.au \
--cc=Ruth.Ivimey-Cook@ivimey.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