From: Andrew Morton <akpm@zip.com.au>
To: Steve Hill <steve@navaho.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Oops in ReiserFS (2.4.17)
Date: Wed, 13 Mar 2002 01:51:08 -0800 [thread overview]
Message-ID: <3C8F210C.C3F1681C@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0203130921070.31433-100000@sorbus.navaho>
Steve Hill wrote:
>
> I keep getting ResierFS oopses on my test box here. It's a Cobalt Raq4i
> running the 2.4.17 kernel (with some of my own experimental code in the
> kernel but I don'tthink this is the cause of the problem). The box has
> been powercycled and paniced more times than I've had hot dinners so I
> suspect that these oopses are being caused by hard drive corruption. The
> ksymoops output is below:
>
> ...
>
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000006
> ...
>
> >>EIP; c0134c9d <get_hash_table+5d/90> <=====
> Trace; c013536f <getblk+1f/50>
One of the buffer_head addresses (which should have been either a
valid address or zero) in fact had a value of 0x00000002. Single
bit error; probably bad memory/CPU/etc.
-
prev parent reply other threads:[~2002-03-13 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 9:31 Oops in ReiserFS (2.4.17) Steve Hill
2002-03-13 9:51 ` Andrew Morton [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=3C8F210C.C3F1681C@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@navaho.co.uk \
/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