From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tomas Hruby <thruby@few.vu.nl>
Subject: Re: BUGs in mm/rmap.c
Date: Sat, 19 Aug 2006 14:32:43 +0200
Message-ID: <20060819123243.GA7706@fspc268>
References: <20060817021008.GD20340@fspc268> <20060817113826.GL4340@parisc-linux.org> <20060817191932.GA10046@fspc268> <20060817194225.GO4340@parisc-linux.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Tomas Hruby <thruby@gmail.com>, linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from smtp.etmail.cz ([160.218.43.220]:27785 "EHLO smtp.etmail.cz")
	by vger.kernel.org with ESMTP id S1751740AbWHSMcs (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Sat, 19 Aug 2006 08:32:48 -0400
To: Matthew Wilcox <matthew@wil.cx>
Content-Disposition: inline
In-Reply-To: <20060817194225.GO4340@parisc-linux.org>
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Thu, Aug 17, 2006 at 01:42:25PM -0600, Matthew Wilcox wrote:
> On Thu, Aug 17, 2006 at 09:19:32PM +0200, Tomas Hruby wrote:
> > I tried that today again and it crashed with a different error on both
> > kernels, with and without that patch. Here are the logs :
> 
> Could you run memtest86 on this machine?  The errors seem to be memory
> corruption, and it's useful to rule out faulty ram before we start
> chasing bugs.

I was thinking about this as well. I ran memtest86 several times
and it didn't report any errors. The question is whether it proves
anything or not.

		T.