From: Tomas Hruby <thruby@few.vu.nl>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Tomas Hruby <thruby@gmail.com>, linux-fsdevel@vger.kernel.org
Subject: Re: BUGs in mm/rmap.c
Date: Sat, 19 Aug 2006 14:32:43 +0200 [thread overview]
Message-ID: <20060819123243.GA7706@fspc268> (raw)
In-Reply-To: <20060817194225.GO4340@parisc-linux.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.
prev parent reply other threads:[~2006-08-19 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 2:10 BUGs in mm/rmap.c Tomas Hruby
2006-08-17 11:38 ` Matthew Wilcox
2006-08-17 19:19 ` Tomas Hruby
2006-08-17 19:42 ` Matthew Wilcox
2006-08-19 12:32 ` Tomas Hruby [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=20060819123243.GA7706@fspc268 \
--to=thruby@few.vu.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=thruby@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).