From: chip@valinux.com (Chip Salzenberg)
To: lomarcan@tin.it
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCSI Tape Corruption - update 2
Date: Sat, 14 Apr 2001 15:52:50 -0700 [thread overview]
Message-ID: <E14oYuQ-0000gf-00@tytlal> (raw)
In-Reply-To: <Pine.LNX.4.31.0104142043340.1271-100000@eris.discordia.loc>
In-Reply-To: <15063.8582.293619.762113@mercury.st.hmc.edu>
In article <Pine.LNX.4.31.0104142043340.1271-100000@eris.discordia.loc> you write:
>On Fri, 13 Apr 2001, Nate Eldredge wrote:
>> (32 bytes is the size of a cache line.) A memory tester might be
>> something to try (I wrote a simple program that seemed to show the
>> error better than memtest86; can send it if desired.)
>
>Already tried that... this system has passed some 20 hours running
>memtest86...
I suggest you try Cerberus:
https://sourceforge.net/projects/va-ctcs/
which will viciously beat your system to within an inch of its life.
If you have any motherboard problems, they're more likely to show up
with Cerberus than with a simple memtest.
--
Chip Salzenberg - a.k.a. - <chip@valinux.com>
"We have no fuel on board, plus or minus 8 kilograms." -- NEAR tech
next prev parent reply other threads:[~2001-04-14 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 15:55 Nate Eldredge
2001-04-14 8:12 ` Geert Uytterhoeven
2001-04-14 18:45 ` Lorenzo Marcantonio
2001-04-14 22:52 ` Chip Salzenberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-12 15:43 SCSI Tape Corruption - update Gérard Roudier
2001-04-12 20:06 ` SCSI Tape Corruption - update 2 Lorenzo Marcantonio
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=E14oYuQ-0000gf-00@tytlal \
--to=chip@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lomarcan@tin.it \
/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
all inboxes | Powered by JetHome®