public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
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: Tue, 16 Oct 2007 14:35:10 -0400	[thread overview]
Message-ID: <20071016183510.GB25480@redhat.com> (raw)
In-Reply-To: <sa564176ksz.fsf@Toushirou.duckcorp.org>

On Tue, Oct 16, 2007 at 07:17:32PM +0200, Arnaud Fontaine wrote:
 > Hello,
 > 
 > We have often the following error from the kernel:
 > 

 >  sshd[1551] trap invalid opcode rip:2aeacc0677a0 rsp:7fffe0c7e688 error:0
 >  Eeek! page_mapcount(page) went negative! (-1)
 >    page pfn = 7f7a8
 >    page->flags = 400000000001002c
 >    page->count = 1
 >    page->mapping = ffff810056170550
 >    vma->vm_ops = 0xffffffff80667ba0
 >    vma->vm_ops->nopage = _stext+0x7fdf7000/0x20
 >    vma->vm_ops->fault = filemap_fault+0x0/0x450
 >    vma->vm_file->f_op->mmap = generic_file_mmap+0x0/0x50
 > ....
 > 
 > We have tested with different  kernel (2.6.23.1 and 2.6.22) and the same
 > error happens  with different process.  Any idea for knowing  what could
 > cause this error?

Many of these that I've seen have turned out to be a hardware problem.
Try running memtest86+ on that machine for a while.
It doesn't catch all problems, but it will highlight more common memory faults.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-10-16 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 17:17 error: Eeek! page_mapcount(page) went negative! (-1) with different process and kernels Arnaud Fontaine
2007-10-16 18:35 ` Dave Jones [this message]
2007-10-16 23:03   ` Arnaud Fontaine
2007-10-17  2:36     ` Dave Jones
2007-10-18 11:25     ` Goswin von Brederlow

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=20071016183510.GB25480@redhat.com \
    --to=davej@redhat.com \
    --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