From: Valdis.Kletnieks@vt.edu
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Tobias Winter <tobias@linuxdingsda.de>, linux-kernel@vger.kernel.org
Subject: Re: [resolved] kernel bug report 2.6.24-rc8 on core2quad q6600 with debian unstable amd64
Date: Fri, 25 Jan 2008 12:20:30 -0500 [thread overview]
Message-ID: <10703.1201281630@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 25 Jan 2008 09:25:59 EST." <20080125142559.GJ16171@csclub.uwaterloo.ca>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Fri, 25 Jan 2008 09:25:59 EST, Lennart Sorensen said:
> Personally I just don't bother with memtest anymore. The only thing it
> tells you is that you have errors or that you might have errors but it
> didn't find them. It never tells you that you do not have errors and it
> often does miss that you have errors since marginal memory is more
> likely to fail under cpu load it seems which memtest doesn't do.
It's been quite some time since I've gone the "run memtest for 24 hours" route.
However, I still recommend that for odd cases, you let memtest make *one* cycle
through its tests - that's only an hour-ish, and if it hits something, then
you *know* you have some hardware issues to deal with.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-01-25 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 0:14 Tobias Winter
2008-01-24 1:07 ` Stephen Hemminger
2008-01-24 14:45 ` Lennart Sorensen
2008-01-25 10:17 ` [resolved] " Tobias Winter
2008-01-25 14:25 ` Lennart Sorensen
2008-01-25 17:20 ` Valdis.Kletnieks [this message]
2008-01-24 1:15 ` Roland Dreier
2008-01-24 11:21 ` Tobias Winter
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=10703.1201281630@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=tobias@linuxdingsda.de \
/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