linux-kernel - Re: error: Eeek! page_mapcount(page) went negative! (-1) with different process and kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Oct 2007 14:35:10 -0400
From:	Dave Jones <davej@...hat.com>
To:	Arnaud Fontaine <arnaud@...esi.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: error: Eeek! page_mapcount(page) went negative! (-1) with
	different process and kernels

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/