From: Ben Nizette <ben.nizette@iinet.net.au>
To: Oliver Neukum <oliver@neukum.org>
Cc: Matthias Schniedermeyer <ms@citd.de>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
DervishD <lkml@dervishd.net>
Subject: Re: single bit errors on files stored on USB-HDDs via USB2/usb_storage
Date: Sat, 09 Dec 2006 17:11:16 +1100 [thread overview]
Message-ID: <457A5384.9070806@iinet.net.au> (raw)
In-Reply-To: <200612081201.36789.oliver@neukum.org>
>>> Also, you mentioned that the corruption occurs systematically on certain
>>> byte patterns. Therefore it's certainly not related to the cables.
>> It'd guess that too, but who can that say for sure. :-|
>
> You may have a bit pattern that stresses the controllers and suddenly
> a marginal cable may matter.
The errors occur in strings of 0xFFs. From the USB standard:
a “1” is represented by no change in level and a “0” is represented by a
change in level
so this error-infested bytes are effectively long, quiet times on the
wire. I would have thought this would be the _least_ stressful time for
the controllers but maybe they are also more susceptible to noise during
this period.
Regards,
Ben
next prev parent reply other threads:[~2006-12-09 6:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa./xvi+/Ji/HqNkvnGjUt4pIS9goM@ifi.uio.no>
2006-12-07 0:02 ` single bit errors on files stored on USB-HDDs via USB2/usb_storage Robert Hancock
2006-12-07 9:03 ` Matthias Schniedermeyer
[not found] ` <fa.nPT9ZJ5poT8fZx3aWy0MqRK/gto@ifi.uio.no>
[not found] ` <fa.aML3aAeWqfac08XNpQa7Zu0AC8w@ifi.uio.no>
2006-12-08 3:18 ` Robert Hancock
2006-12-08 9:07 ` Matthias Schniedermeyer
2006-12-08 10:25 ` Stefan Richter
2006-12-08 10:39 ` Matthias Schniedermeyer
2006-12-08 11:01 ` Oliver Neukum
2006-12-08 12:27 ` Stefan Richter
2006-12-09 6:11 ` Ben Nizette [this message]
2006-12-09 8:18 ` Oliver Neukum
2006-12-09 10:16 ` Ben Nizette
2006-12-10 8:44 linux
2006-12-10 15:37 ` Clemens Koller
-- strict thread matches above, loose matches on Subject: below --
2006-12-07 18:08 [usb-storage] " Alan Stern
2006-12-07 19:41 ` Matthias Schniedermeyer
2006-12-07 23:45 ` Pete Zaitcev
2006-12-08 9:16 ` Matthias Schniedermeyer
2006-12-08 12:21 ` Stefan Richter
2006-12-08 16:18 ` John Stoffel
2006-12-06 22:01 Matthias Schniedermeyer
2006-12-07 22:10 ` DervishD
2006-12-07 22:57 ` Matthias Schniedermeyer
2006-12-07 23:05 ` Jan Engelhardt
2006-12-08 9:32 ` DervishD
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=457A5384.9070806@iinet.net.au \
--to=ben.nizette@iinet.net.au \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.net \
--cc=ms@citd.de \
--cc=oliver@neukum.org \
--cc=stefanr@s5r6.in-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.