From: ken <koehlekr@ucrwcu.rwc.uc.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 multiple Oops and file corruption on I845 MB
Date: Thu, 24 Jan 2002 17:09:04 -0500 [thread overview]
Message-ID: <3C508600.25AF021@ucrwcu.rwc.uc.edu> (raw)
Hi Folks,
Well, I guess I'm not the only one who has ever had egg on his face
after posting a bug report.
Before posting the report, I had run memtest86 v2.5.1 for more than one
complete pass of the std tests and had concluded the memory was OK. On
a hunch, after a reply from Mark Hahn, I let it run all night; after 17
hours running all tests over 3+ passes, it recorded about 4000 errors.
These were clustered around 64MB and 135MB (64K and 4K holes,
respectively), and I think that adequately accounts for the problems I
was having on large file copies. The guy who sold me the hardware took
it all back and refunded my money rather than having to learn something
about linux, so I guess he didn't deserve the sale after all.
Thanks again to all who read and responded. Now I know to run multiple
passes on memtest before deciding things are OK....
Ken
next reply other threads:[~2002-01-24 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 22:09 ken [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-23 16:28 Ken
2002-01-24 18:54 ` Denis Vlasenko
2002-01-24 20:52 ` Andrew Morton
2002-01-27 19:47 ` Alan Cox
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=3C508600.25AF021@ucrwcu.rwc.uc.edu \
--to=koehlekr@ucrwcu.rwc.uc.edu \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome