| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAJBHPojqskwn4Q_i2BsGgAC-FK+BVn8n=htvSJ72tuLgd-S6Vg@mail.gmail.com>
Date: Mon, 28 Sep 2015 21:42:04 +0200
From: Marcus Overhagen <marcus.overhagen@...il.com>
To: kernel list <linux-kernel@...r.kernel.org>
Cc: linux-mmc@...r.kernel.org, Lee Jones <lee.jones@...aro.org>
Subject: Fwd: Data corruption with RTS5129 card reader and 128 GB SDXC microsd
Can somebody help me with this issue? Linux is corrupting data when
using the SD card reader!
I already sent it to linux-mmc on September 11th, and on September
17th forwarded it to Roger Tseng (author of rtsx_usb) and Samuel Ortiz
(maintainer of MFD) but have received no response,
---------- Forwarded message ----------
From: Marcus Overhagen <marcus.overhagen@...il.com>
Date: Fri, Sep 11, 2015 at 3:26 PM
Subject: Data corruption with RTS5129 card reader and 128 GB SDXC microsd
To: linux-mmc@...r.kernel.org
I have a data corruption problem with RTS5129 sd card reader and a
128GB Samsung EVO microsd.
This is not a fake card, its tested ok with H2testw in another windows machine.
The card also works when I put it in an external microSD=>USB card reader.
Previously I was using a 32 GB Sandisk Ultra microsd UHS-I without
noticing any issues.
With the 128GB card, playback of dashcam videos shows many broken
frames, but is ok when using external card reader.
A test with F3 software shows "overwritten" sectors, I think in this
case they indicate that the wrong sector is read.
Bus 003 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129
Card Reader Controller
[root@...tterdaemmerung marcus]# uname -a
Linux goetterdaemmerung 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17
08:52:28 CEST 2015 x86_64 GNU/Linux
[ 1.033568] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 1.033575] xhci_hcd 0000:00:14.0: new USB bus registered, assigned
bus number 3
[ 1.033673] xhci_hcd 0000:00:14.0: hcc params 0x20007181 hci
version 0x100 quirks 0x0000b930
[ 1.033682] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 1.033931] hub 3-0:1.0: USB hub found
[ 1.393530] usb 3-3: new high-speed USB device number 2 using xhci_hcd
[ 1.451468] hub 1-1:1.0: USB hub found
[ 1.451580] hub 1-1:1.0: 6 ports detected
[ 1.464698] hub 2-1:1.0: USB hub found
[ 1.464847] hub 2-1:1.0: 6 ports detected
[ 1.572914] usbcore: registered new interface driver rtsx_usb
[67697.876276] mmc0: new ultra high speed SDR50 SDXC card at address 59b4
[67697.876720] mmcblk0: mmc0:59b4 00000 119 GiB
[67697.881189] mmcblk0: p1
some errors are loggged during card access:
[68223.345521] mmcblk0: error -110 sending stop command, original cmd
response 0x900, card status 0x900
[68224.446561] mmcblk0: error -110 sending stop command, original cmd
response 0x900, card status 0x900
[68247.455199] mmcblk0: error -110 sending stop command, original cmd
response 0x900, card status 0x900
read test errors:
[root@...tterdaemmerung f3-5.0]# mount /dev/mmcblk0p1 /mnt/dashcam1/
FUSE exfat 1.1.0
[root@...tterdaemmerung f3-5.0]# ./f3read /mnt/dashcam1/
SECTORS ok/corrupted/changed/overwritten
Validating file 1.h2w ... 2096266/ 184/ 0/ 702
Validating file 2.h2w ... 2096567/ 2/ 0/ 583
Validating file 3.h2w ... 2097151/ 1/ 0/ 0
Validating file 4.h2w ... 213984/ 0/ 0/ 0^C
after unmounting and mounting it again, the result is different:
FUSE exfat 1.1.0
[root@...tterdaemmerung f3-5.0]# ./f3read /mnt/dashcam1/
SECTORS ok/corrupted/changed/overwritten
Validating file 1.h2w ... 2096546/ 370/ 0/ 236
Validating file 2.h2w ... 2096074/ 6/ 0/ 1072
Validating file 3.h2w ... 2095924/ 252/ 0/ 976
Validating file 4.h2w ... 1295451/ 0/ 0/ 901^C
I got the impression yesterday that writing to the card results in
much more errors.
Thus today for this tests, data on the card was written with the other
windows machine and is 100% correct.
What can I do? What other information should I provide?
For comparision, this is the working external sd-card=>USB hardware :
Bus 003 Device 011: ID aaaa:8816 MXT
or
Bus 003 Device 014: ID 0781:b7b1 SanDisk Corp.
[64645.868255] usb 3-4: new high-speed USB device number 15 using xhci_hcd
[64646.057349] usb-storage 3-4:1.0: USB Mass Storage device detected
[64646.057594] scsi host14: usb-storage 3-4:1.0
[64647.060934] scsi 14:0:0:0: Direct-Access Generic STORAGE
DEVICE 9407 PQ: 0 ANSI: 0
[64647.682113] sd 14:0:0:0: [sdb] 251131904 512-byte logical blocks:
(128 GB/119 GiB)
[64647.682986] sd 14:0:0:0: [sdb] Write Protect is off
[64647.682993] sd 14:0:0:0: [sdb] Mode Sense: 03 00 00 00
[64647.683957] sd 14:0:0:0: [sdb] No Caching mode page found
[64647.683966] sd 14:0:0:0: [sdb] Assuming drive cache: write through
[64647.690645] sdb: sdb1
[64647.693784] sd 14:0:0:0: [sdb] Attached SCSI removable disk
[root@...tterdaemmerung f3-5.0]# mount /dev/sdb1 /mnt/dashcam1/
FUSE exfat 1.1.0
[root@...tterdaemmerung f3-5.0]# ./f3read /mnt/dashcam1/
SECTORS ok/corrupted/changed/overwritten
Validating file 1.h2w ... 2097152/ 0/ 0/ 0
Validating file 2.h2w ... 2097152/ 0/ 0/ 0
Validating file 3.h2w ... 2097152/ 0/ 0/ 0
Validating file 4.h2w ... 2097152/ 0/ 0/ 0
Validating file 5.h2w ... 2097152/ 0/ 0/ 0
Validating file 6.h2w ... 2097152/ 0/ 0/ 0
Validating file 7.h2w ... 2097152/ 0/ 0/ 0
Validating file 8.h2w ... 2097152/ 0/ 0/ 0
Validating file 9.h2w ... 2097152/ 0/ 0/ 0
Validating file 10.h2w ... 2097152/ 0/ 0/ 0
Validating file 11.h2w ... 1080288/ 0/ 0/ 0^C
[root@...tterdaemmerung f3-5.0]#
And this is when I tested the microSD card with another machine using
H2testw in windows and it's ok:
> Achtung: Nur 122590 von 122591 MByte getestet.
> Fertig, kein Fehler aufgetreten.
> Sie können die Testdateien *.h2w jetzt löschen oder nach Belieben
> nochmals überprüfen.
> Schreibrate: 18,6 MByte/s
> Leserate: 41,3 MByte/s
> H2testw v1.4
regards
Marcus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists