From: Len Brown <lenb@kernel.org>
To: "Jan-Simon Möller" <dl9pf@gmx.de>
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
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory
Date: Tue, 11 Mar 2008 13:23:11 -0400 [thread overview]
Message-ID: <200803111323.11524.lenb@kernel.org> (raw)
In-Reply-To: <200803101959.47202.dl9pf@gmx.de>
> +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) .
next prev parent reply other threads:[~2008-03-11 17:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 12:21 [PATCH 2.6.24] mm: BadRAM support for broken memory devzero
2008-03-04 13:27 ` Ingo Molnar
2008-03-04 13:43 ` Rick van Rein
2008-03-04 14:06 ` Ingo Molnar
2008-03-04 15:05 ` Pavel Machek
2008-03-08 10:27 ` H. Peter Anvin
2008-03-08 11:13 ` Jiri Kosina
2008-03-10 10:12 ` Jan-Simon Möller
2008-03-10 11:24 ` Jan-Simon Möller
2008-03-10 11:52 ` Pavel Machek
2008-03-10 14:23 ` Jan-Simon Möller
2008-03-10 17:20 ` H. Peter Anvin
2008-03-10 17:48 ` Jan-Simon Möller
2008-03-10 18:59 ` Jan-Simon Möller
2008-03-10 19:16 ` Jan-Simon Möller
2008-03-10 22:56 ` Pavel Machek
2008-03-11 0:37 ` Jan-Simon Möller
2008-03-11 17:23 ` Len Brown [this message]
2008-03-11 17:49 ` Jan-Simon Möller
2008-03-11 19:24 ` Johannes Weiner
2008-03-11 20:00 ` Jan-Simon Möller
2008-03-10 22:07 ` Rick van Rein
2008-03-11 0:41 ` Jan-Simon Möller
2008-03-11 6:41 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2008-03-04 14:00 devzero
2008-03-02 13:42 Rick van Rein
2008-03-02 17:01 ` KOSAKI Motohiro
2008-03-02 17:42 ` Rick van Rein
2008-03-03 3:21 ` KOSAKI Motohiro
2008-03-03 5:32 ` Nick Piggin
2008-03-03 7:14 ` KOSAKI Motohiro
2008-03-03 7:35 ` Nick Piggin
2008-03-03 9:49 ` KOSAKI Motohiro
2008-03-03 9:58 ` KAMEZAWA Hiroyuki
2008-03-02 17:53 ` Joseph Fannin
2008-03-02 19:34 ` Rick van Rein
2008-03-03 14:14 ` Pavel Machek
2008-03-03 16:41 ` KOSAKI Motohiro
2008-03-08 10:25 ` H. Peter Anvin
2008-03-08 10:30 ` H. Peter Anvin
2008-03-03 17:38 ` Randy Dunlap
[not found] ` <20080303082238.GB13580@elte.hu>
[not found] ` <47CC3005.5090706@zytor.com>
[not found] ` <20080304133028.GC32383@elte.hu>
2008-03-04 16:29 ` H. Peter Anvin
2008-03-04 16:47 ` Ingo Molnar
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=200803111323.11524.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=devzero@web.de \
--cc=dl9pf@gmx.de \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rick@vanrein.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