On 24 Jun 2003, Chris Mason said:
> 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.
Ah. That does sound like either bad RAM or scattershot corruption.
> 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.
Done that, no problems found. (Most drives are e3fs.)
2.4.21's crashed once more since then, network driver death; I'm
probably going to revert to 2.4.20 on that box, which ran perfectly
since three days past 2.4.20's release. (However, several other boxes
had problems with 2.4.20 which were cleared up with .21... you win some,
you lose some. I'd say this has been a net gain.)
I'll see if 2.4.20 has the same problems; if it does, then I agree, the
RAM's probably had it.
--
`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
-
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/