From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nix Subject: Re: 2.4.21 reiserfs oops Date: Mon, 23 Jun 2003 23:16:27 +0100 Message-ID: <87k7bcxww4.fsf@amaterasu.srvr.nix> References: <87he6iyzyj.fsf@amaterasu.srvr.nix> <20030623095356.GA12936@namesys.com> Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <20030623095356.GA12936@namesys.com> (Oleg Drokin's message of "Mon, 23 Jun 2003 13:53:56 +0400") List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Oleg Drokin Cc: Linux Kernel Development , reiserfs-list@namesys.com On Mon, 23 Jun 2003, Oleg Drokin said: > Hello! > > On Sun, Jun 22, 2003 at 03:00:20PM +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. >> Jun 22 13:52:43 loki kernel: EIP: 0010:[] 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. All my other boxes love 2.4.21, but this one dislikes it. (Of course it has to be my second-most-critical server... ah well, the NFS problems in 2.4.20 bit my most critical server and my home directory both, so I guess this is less unpleasant.) > Can you run memtest86 for some time to verify that your RAM is OK? Did that last night; no problems reported. (Not really surprising.) > (hm, and the oops got twice to the logs which is pretty strange thing, too, > never seen anything like this). That's my weirdly broken syslog config. I've never got around to fixing it; it only happens with kernel messages and I don't get all that many of those. -- `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