mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Thu, 18 Oct 2007 13:25:55 +0200	[thread overview]
Message-ID: <87y7e0mzp8.fsf@informatik.uni-tuebingen.de> (raw)
In-Reply-To: <sa5ejfu64t5.fsf@Toushirou.duckcorp.org> (Arnaud Fontaine's message of "Wed, 17 Oct 2007 01:03:02 +0200")

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

      parent reply	other threads:[~2007-10-18 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 17:17 Arnaud Fontaine
2007-10-16 18:35 ` Dave Jones
2007-10-16 23:03   ` Arnaud Fontaine
2007-10-17  2:36     ` Dave Jones
2007-10-18 11:25     ` Goswin von Brederlow [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y7e0mzp8.fsf@informatik.uni-tuebingen.de \
    --to=brederlo@informatik.uni-tuebingen.de \
    --cc=arnaud@andesi.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®