public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.demon.co.uk>
To: Oleg Drokin <green@namesys.com>
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 21:34:55 +0100	[thread overview]
Message-ID: <8765mvxlhs.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20030624053129.GA24025@namesys.com> (Oleg Drokin's message of "Tue, 24 Jun 2003 09:31:29 +0400")

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 
>> > 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?

Different boots. I upgraded, the first boot crashed within five minutes
with weird SCSI errors, so I rebooted again and this happened six hours
later.

I'm willing to write off the SCSI errors to the shock effect of having
just been powered down for the first time in a year (the shutdown
scripts didn't quite work and the reset button is disconnected).

>> 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?

No obvious sign of it:

  9:34pm  up 1 day 22:30,  14 users,  load average: 0.09, 0.12, 0.16

(it is of course waiting until I am hundreds of miles away. *Then* it'll
crash.)

-- 
`It is an unfortunate coincidence that the date locarchive.h was
 written (in hex) matches Ritchie's birthday (in octal).'
               -- Roland McGrath on the libc-alpha list

  reply	other threads:[~2003-06-24 20:46 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 [this message]
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=8765mvxlhs.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.demon.co.uk \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --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