From: Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>
To: Arnaud Fontaine <arnaud@andesi.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: error: Eeek! page_mapcount(page) went negative! (-1) with  different process and kernels
References: <sa564176ksz.fsf@Toushirou.duckcorp.org>
	<20071016183510.GB25480@redhat.com>
	<sa5ejfu64t5.fsf@Toushirou.duckcorp.org>
Date: Thu, 18 Oct 2007 13:25:55 +0200
In-Reply-To: <sa5ejfu64t5.fsf@Toushirou.duckcorp.org> (Arnaud Fontaine's
	message of "Wed, 17 Oct 2007 01:03:02 +0200")
Message-ID: <87y7e0mzp8.fsf@informatik.uni-tuebingen.de>
User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1180
Lines: 30

Arnaud Fontaine <arnaud@andesi.org> writes:

>>>>>> "Dave" == Dave Jones <davej@redhat.com> writes:
>
>     Dave> Many of these that I've  seen have turned out to be a hardware
>     Dave> problem.  Try running memtest86+  on that machine for a while.
>     Dave>  It doesn't  catch all  problems, but  it will  highlight more
>     Dave> common memory faults.
>
> Hello,
>
> We ran memtest86+ before production, it  was about one month ago. Do you
> think it could come from that anyway?

I find that a lot of the time memtest does not reveal an error. Only
when you combine multiple sources or on random access do you get
errors. For example compiling a kernel while doing heavy I/O on the
disk. But that might just be me. Errors are rather random occurances.

Compiling a kernel repeadatly and multiple in parallel is usualy a
good test. If it sometimes fails to compile then it is near certain a
hardware error.

MfG
        Goswin
-
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/