From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-kernel@vger.kernel.org
Subject: Re: unexplainable read errors, copy/diff-issue
Date: Mon, 13 Nov 2006 04:23:53 +0100 [thread overview]
Message-ID: <4557E549.1080506@scientia.net> (raw)
In-Reply-To: <20061110135649.16cccca0.vsu@altlinux.ru>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
I may have probably found the bug,.. or at least some valuable
information about it.
It seems like it's actually the DMA who is responsible for the errors.
Until now I've completed 3 rund where I validated all files via their
sha512 sums,... and no errors were found.
I did this only on the PATA drives,... not yet on the SATA drives (and
remember, the issue happened on both drive types)
1) How do I deactivate DMA for an SATA drive?
2) How can I find out definitely if Windows uses DMA for a drive or not.
The hardware management shows for the primary IDE controller an
activated DMA. But the diff was so slow under Windows, that I assume
that this may be wrong.
Does this give you any further idea about the possible reason for the
issue? Is it possible a driver error (for that specific chipsets)? Or
hardware error?
Or can I try any other things?
Thanks and best wishes,
Chris.
[-- Attachment #2: calestyo.vcf --]
[-- Type: text/x-vcard, Size: 156 bytes --]
begin:vcard
fn:Mitterer, Christoph Anton
n:Mitterer;Christoph Anton
email;internet:calestyo@scientia.net
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2006-11-13 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 2:01 unexplainable read errors, copy/diff-issue Christoph Anton Mitterer
2006-11-10 10:56 ` Sergey Vlasov
2006-11-11 16:35 ` Christoph Anton Mitterer
2006-11-12 20:44 ` Christoph Anton Mitterer
2006-11-12 23:32 ` Christoph Anton Mitterer
[not found] ` <20061113000120.09fd6174@localhost.localdomain>
2006-11-13 20:59 ` Christoph Anton Mitterer
2006-11-13 3:23 ` Christoph Anton Mitterer [this message]
2006-11-24 11:11 ` Christoph Anton Mitterer
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=4557E549.1080506@scientia.net \
--to=calestyo@scientia.net \
--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