From: Oleg Drokin <green@namesys.com>
To: Nix <nix@esperi.demon.co.uk>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
reiserfs-list@namesys.com
Subject: Re: 2.4.21 reiserfs oops
Date: Tue, 24 Jun 2003 09:31:29 +0400 [thread overview]
Message-ID: <20030624053129.GA24025@namesys.com> (raw)
In-Reply-To: <87k7bcxww4.fsf@amaterasu.srvr.nix>
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.
> >> Jun 22 13:52:43 loki kernel: EIP: 0010:[<c0092df4>] Not tainted
> > And the EIP is prior to kernel start which is also very strange.
> > On the other hand the address c0192df4 is somewhere inside reiserfs code,
> > so it looks like a single bit error, I'd say.
> I think it unlikely to be RAM problems given that the problem happened
> shortly after upgrading to 2.4.21; this was about half a day after I
> rebooted it because it threw a pile of never-seen-again, un-syslogged
> SCSI abort errors at me (sym53c875); and *that* was a few minutes after
> I rebooted into 2.4.21 for the first time.
Hm, so first there were some scsi problems and then reiserfs oops?
Actually since the RAM is good, I see no good reason for this to happen.
(actually I see no good reason for valid code before _text, either).
I wonder if 2.4.21 constantly crashes like that for you, then?
Bye,
Oleg
next prev parent reply other threads:[~2003-06-24 5:31 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 [this message]
2003-06-24 20:34 ` Nix
2003-06-24 21:09 ` Chris Mason
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=20030624053129.GA24025@namesys.com \
--to=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 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.