> Do you encounter actual read errors (that is, error messages in the > system log), or do you find that the reads appear to succeed but return > incorrect data? Yes, the reads succeed but return incorrect data
> If you write data under 2.6.22 and then read it back with 2.6.17, does > it come out okay? Yes, it does. > If you read the same data back multiple times under 2.6.22, do the same > CRC/MD5 errors occur each time? Or do you get a different set of > mismatches? Each time I get different md5-s > Have you tried running the intermediate development testing kernels > between 2.6.17 and 2.6.18? For example, what happens with 2.6.18-rc1? 2.6.17.14 - works fine 2.6.18-rc1 - same as 2.6.18 (incorrect data) Data is not all incorrect in files copied from the Flash Drive. It only contains some set of random error blocks. For a simple example, a movie-file (mp4, xVid) plays well (not on every players), but some frames is "broken". The size of a file does not change. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
