linux-kernel - Re: [resolved] kernel bug report 2.6.24-rc8 on core2quad q6600 with debian unstable amd64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <10703.1201281630@turing-police.cc.vt.edu>
Date:	Fri, 25 Jan 2008 12:20:30 -0500
From:	Valdis.Kletnieks@...edu
To:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
Cc:	Tobias Winter <tobias@...uxdingsda.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [resolved] kernel bug report 2.6.24-rc8 on core2quad q6600 with debian unstable amd64

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.

Content of type "application/pgp-signature" skipped