Messages in this thread | | | Date | Tue, 24 Jun 2003 09:31:29 +0400 | From | Oleg Drokin <> | Subject | Re: 2.4.21 reiserfs oops |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |