From: Len Brown <lenb@kernel.org>
Organization: Intel Open Source Technology Center
To: Jan-Simon =?iso-8859-1?q?M=F6ller?= <dl9pf@gmx.de>
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory
Date: Tue, 11 Mar 2008 13:23:11 -0400
User-Agent: KMail/1.9.9
Cc: "H. Peter Anvin" <hpa@zytor.com>, Pavel Machek <pavel@ucw.cz>,
       Jiri Kosina <jkosina@suse.cz>, Ingo Molnar <mingo@elte.hu>,
       devzero@web.de, linux-kernel@vger.kernel.org, rick@vanrein.org
References: <182234194@web.de> <47D56DD3.8060108@zytor.com> <200803101959.47202.dl9pf@gmx.de>
In-Reply-To: <200803101959.47202.dl9pf@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803111323.11524.lenb@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 724
Lines: 24


> +How to deal with bad memory e.g. reported by memtest86+ ?
> +#########################################################
> +
> +There are three possibilities I know of:

I find that sometimes memory problems go away when
I simply remove and then re-insert the same DIMMs.
Maybe that is the thing to try first.

-Len

> +1) Buy new memory (best!)
> +
> +2) Try to exchange the memory if you have spare-parts
> +
> +3) Use BadRAM or memmap
> +
> +This Howto is about number 3) .
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/