This sounds like what mine was doing, the oops looked similar as well
(with the null pointer part atleast).  Reboot and I bet it'll run fine
for a while and then start up again.  For me it seemed to start faulting
when "free" showed over 250 Megs used.


Thus spake Jacek Kawa (jfk@zeus.polsl.gliwice.pl):

> Jak podaj? anonimowe ?r?d?a, przepowiedziano, ?e Jacek Kawa napisze:
> 
> > This machine has new RAM, but after about 7 hours of testing, 
> > memtest.86 didn't show any errors... 
> 
> Well, it's RAM anyway... I've just got few segfaults in vim...
> 
> bye
> 
> -- 
> Jacek Kawa
> -
> 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/

:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Life is not a destination, it's a journey.
  Microsoft produces 15 car pileups on the highway.
    Don't stop traffic to stand and gawk at the tragedy.