From: Chris Mason <mason@suse.com>
To: Nix <nix@esperi.demon.co.uk>
Cc: Oleg Drokin <green@namesys.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
reiserfs-list@namesys.com
Subject: Re: 2.4.21 reiserfs oops
Date: 24 Jun 2003 17:09:26 -0400 [thread overview]
Message-ID: <1056488965.10097.60.camel@tiny.suse.com> (raw)
In-Reply-To: <8765mvxlhs.fsf@amaterasu.srvr.nix>
On Tue, 2003-06-24 at 16:34, Nix wrote:
> On Tue, 24 Jun 2003, Oleg Drokin moaned:
> > Hello!
> >
> > On Mon, Jun 23, 2003 at 11:16:27PM +0100, Nix wrote:
> >
> >> >> Jun 22 13:52:42 loki kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000001
> >> > This is very strange address to oops on.
> >> I'll say! Looks almost like it JMPed to a null pointer or something.
> >
> > No, if it'd jumped to a NULL pointer, we'd see 0 in EIP.
>
> JMPed to ((long)NULL)+1 or something then :) the fact remains that it's
> not somewhere that even a memory error would make us likely to jump to.
>
> >> >> Jun 22 13:52:43 loki kernel: EIP: 0010:[<c0092df4>] Not tainted
The EIP isn't zero or 1, you've got a bad null pinter dereference at
address 1. You get this when you do something like *(char *)1 =
some_val.
The ram is most likely bad, you're 1 bit away from zero, but you might
try a reiserfsck on any drives affected by the scsi errors.
-chris
next prev parent reply other threads:[~2003-06-24 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 14:00 2.4.21 reiserfs oops Nix
2003-06-23 9:53 ` Oleg Drokin
2003-06-23 22:16 ` Nix
2003-06-24 5:31 ` Oleg Drokin
2003-06-24 20:34 ` Nix
2003-06-24 21:09 ` Chris Mason [this message]
2003-06-25 21:47 ` Nix
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=1056488965.10097.60.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.demon.co.uk \
--cc=reiserfs-list@namesys.com \
/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