mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Newall <david@davidnewall.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Richard D <richard@embunus.com>,
	"'Matthew Bloch'" <matthew@bytemark.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Testing RAM from userspace / question about memmap= arguments
Date: Sun, 23 Dec 2007 07:06:58 +1030	[thread overview]
Message-ID: <476D756A.6060507@davidnewall.com> (raw)
In-Reply-To: <20071222184759.GB31809@elf.ucw.cz>

Pavel Machek wrote:
> memtest has following problems:
>
> 	0) it is kind of hard to run memtest over ssh
>   

It's kind of hard to run anything over SSH if it has to be run before 
userspace is up.  But the kernel can collect results from a modified 
memtest, after it chains back.

> 	1) if linux fixes some problem with PCI quirk or microcode
> 	upload, memtest will not see the fix
>   

What are you saying?  Linux is going to fix faulty RAM?  The point with 
testing RAM is you *want* to see it fail; you don't want Linux to fix it.

> 	2) if memory only fails while something else happens (DMA to
> 	other piece of memory? Hard disk load glitching powre
> 	supply?), memtest will not see the problem.

These are not RAM faults.  The very last thing you want is evidence that 
you've got a faulty piece of RAM when the fault is actually a hard disk 
glitch!

  reply	other threads:[~2007-12-22 20:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 17:06 Matthew Bloch
2007-12-20 12:33 ` Jon Masters
2007-12-20 14:17   ` Matthew Bloch
2007-12-21 12:58 ` Pavel Machek
2007-12-22  8:12   ` Richard D
2007-12-22 13:46     ` Pavel Machek
2007-12-22 15:30       ` Richard D
2007-12-22 18:43         ` Pavel Machek
2007-12-22 16:06       ` David Newall
2007-12-22 18:47         ` Pavel Machek
2007-12-22 20:36           ` David Newall [this message]
2007-12-22 20:54             ` Pavel Machek
2007-12-23  7:35               ` David Newall
2007-12-23 11:17                 ` Pavel Machek
2007-12-22 20:48         ` Matthew Bloch
2007-12-22 20:09 ` Arjan van de Ven
2007-12-25 23:09   ` Pavel Machek
2007-12-26 10:17     ` Arjan van de Ven
2007-12-26 20:37       ` Maxim Levitsky
2007-12-20 17:01 Siva Prasad

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=476D756A.6060507@davidnewall.com \
    --to=david@davidnewall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@bytemark.co.uk \
    --cc=pavel@ucw.cz \
    --cc=richard@embunus.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

Powered by JetHome