Looks Like The Is A Read/timing Problem With Sd Reading When High Cpu

[Polossatik]

I just provoked the I/O with an OTHER SD card who never gave issues before (was always tested in the right slot).

On my system I can still NOT simulate this at will with ALL cards, but things that look like they play:

* the pandora is restarted (it seams to repro better after a reboot) with wifi enabled and auto connect to wifi network
* you test (DD) the SD card in the LEFT slot
* you generate traffic (start the browser) for the FIRST time (I assume this is waking up the wifi chip or so , might be that after X time of no use you can have this again)

testing (dd'ing) the RIGHT slot card never gave (so far) any of those I/O errors on my system (even not using the Sd card that always give an I/O error in the left slot).

 

[Pleng]

OK quick update. I only appear to get this issue when moving files from a Class 4 card to a Class 2 card. Moving files from the Class 2 card to the Class 4 works flawlessly.

Is it possible that the controller is not negotiating an appropriate transfer speed and thus tripping up on itself somehow by trying to send too much data at once?

 

[zapman]

ah, 'nice' to see that there are other people having the same problem.

I just got aware of it after trying to copy the contents of a 16GB card in slot 1 (extrememory from EDs shop, class 6) to a 32GB card in slot 2 (takeMS card, class 6). Lots of big files (wesnoth.pnd, the source files of quake2 and quake3) got corrupted in the process: they are all around 20 to 70 MB now...

# I'm using hotfix3 and copied the files with the file manager.
# Having FAT or ext2 on the 16GB card does not make any difference, same problem.
# Retrying to copy the same file several times leads to different file sizes in the destination folder. So the error is not bit-specific.
# I have an ideling system. No CPU stress is needed to produce the IO error.
# The errors appear also with WiFi switched off.

dmesg output:

tusters_kasten:~$ dmesg
ci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.546936] mmcblk0: error -84 transferring data
[  213.551666] end_request: I/O error, dev mmcblk0, sector 18064272
[  213.557739] end_request: I/O error, dev mmcblk0, sector 18064280
[  213.672821] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.672912] mmcblk0: error -84 transferring data
[  213.677673] end_request: I/O error, dev mmcblk0, sector 18065496
[  213.683746] end_request: I/O error, dev mmcblk0, sector 18065504
[  213.722412] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.722503] mmcblk0: error -84 transferring data
[  213.727172] end_request: I/O error, dev mmcblk0, sector 18065840
[  213.733245] end_request: I/O error, dev mmcblk0, sector 18065848
[  213.744781] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.744903] mmcblk0: error -84 transferring data
[  213.749572] end_request: I/O error, dev mmcblk0, sector 18065896
[  213.755615] end_request: I/O error, dev mmcblk0, sector 18065904
[  213.770935] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.771026] mmcblk0: error -84 transferring data
[  213.775787] end_request: I/O error, dev mmcblk0, sector 18066000
[  213.781860] end_request: I/O error, dev mmcblk0, sector 18066008
[  213.814361] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.814727] mmcblk0: error -84 transferring data
[  213.819427] end_request: I/O error, dev mmcblk0, sector 18066344
[  213.825500] end_request: I/O error, dev mmcblk0, sector 18066352
[  213.853393] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.853790] mmcblk0: error -84 transferring data
[  213.858489] end_request: I/O error, dev mmcblk0, sector 18066640
[  213.864532] end_request: I/O error, dev mmcblk0, sector 18066648
[  213.876617] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.877746] mmcblk0: error -84 transferring data
[  213.882415] end_request: I/O error, dev mmcblk0, sector 18066712
[  213.888488] end_request: I/O error, dev mmcblk0, sector 18066720
[  213.910217] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.910308] mmcblk0: error -84 transferring data
[  213.914978] end_request: I/O error, dev mmcblk0, sector 18066816
[  213.921051] end_request: I/O error, dev mmcblk0, sector 18066824
[  213.928588] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.928680] mmcblk0: error -84 transferring data
[  213.933380] end_request: I/O error, dev mmcblk0, sector 18066816
[  213.950775] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  213.950836] mmcblk0: error -84 transferring data
[  213.955566] end_request: I/O error, dev mmcblk0, sector 18066928
[  214.004089] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  214.004180] mmcblk0: error -84 transferring data
[  214.008850] end_request: I/O error, dev mmcblk0, sector 18067376
[  249.402862] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  249.403228] mmcblk0: error -84 transferring data
[  249.407958] end_request: I/O error, dev mmcblk0, sector 18067656
[  249.414001] end_request: I/O error, dev mmcblk0, sector 18067664
[  249.420043] end_request: I/O error, dev mmcblk0, sector 18067672
[  249.426086] end_request: I/O error, dev mmcblk0, sector 18067680
[  249.432128] end_request: I/O error, dev mmcblk0, sector 18067688
[  249.438171] end_request: I/O error, dev mmcblk0, sector 18067696
[  249.444213] end_request: I/O error, dev mmcblk0, sector 18067704
[  249.450256] end_request: I/O error, dev mmcblk0, sector 18067712
[  249.456298] end_request: I/O error, dev mmcblk0, sector 18067720
[  249.462341] end_request: I/O error, dev mmcblk0, sector 18067728
[  249.468383] end_request: I/O error, dev mmcblk0, sector 18067736
[  249.474426] end_request: I/O error, dev mmcblk0, sector 18067744
[  249.480468] end_request: I/O error, dev mmcblk0, sector 18067752
[  249.486511] end_request: I/O error, dev mmcblk0, sector 18067760
[  249.492553] end_request: I/O error, dev mmcblk0, sector 18067768
[  249.498596] end_request: I/O error, dev mmcblk0, sector 18067776
[  249.512725] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  249.513122] mmcblk0: error -84 transferring data
[  249.517822] end_request: I/O error, dev mmcblk0, sector 18067912
[  249.523895] end_request: I/O error, dev mmcblk0, sector 18067920
[  249.529937] end_request: I/O error, dev mmcblk0, sector 18067928
[  249.535980] end_request: I/O error, dev mmcblk0, sector 18067936
[  249.542022] end_request: I/O error, dev mmcblk0, sector 18067944
[  249.548065] end_request: I/O error, dev mmcblk0, sector 18067952
[  249.554107] end_request: I/O error, dev mmcblk0, sector 18067960
[  249.560150] end_request: I/O error, dev mmcblk0, sector 18067968
[  249.566192] end_request: I/O error, dev mmcblk0, sector 18067976
[  249.572235] end_request: I/O error, dev mmcblk0, sector 18067984
[  249.578277] end_request: I/O error, dev mmcblk0, sector 18067992
[  249.584320] end_request: I/O error, dev mmcblk0, sector 18068000
[  249.590362] end_request: I/O error, dev mmcblk0, sector 18068008
[  249.596405] end_request: I/O error, dev mmcblk0, sector 18068016
[  249.602447] end_request: I/O error, dev mmcblk0, sector 18068024
[  249.608489] end_request: I/O error, dev mmcblk0, sector 18068032
[  249.675445] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  249.713531] mmcblk0: error -84 transferring data
[  249.718200] end_request: I/O error, dev mmcblk0, sector 18068168
[  249.724273] end_request: I/O error, dev mmcblk0, sector 18068176
[  249.730316] end_request: I/O error, dev mmcblk0, sector 18068184
[  249.736358] end_request: I/O error, dev mmcblk0, sector 18068192
[  249.742401] end_request: I/O error, dev mmcblk0, sector 18068200
[  249.748443] end_request: I/O error, dev mmcblk0, sector 18068208
[  249.754486] end_request: I/O error, dev mmcblk0, sector 18068216
[  249.760528] end_request: I/O error, dev mmcblk0, sector 18068224
[  249.766571] end_request: I/O error, dev mmcblk0, sector 18068232
[  249.772613] end_request: I/O error, dev mmcblk0, sector 18068240
[  249.778656] end_request: I/O error, dev mmcblk0, sector 18068248
[  249.784698] end_request: I/O error, dev mmcblk0, sector 18068256
[  249.790740] end_request: I/O error, dev mmcblk0, sector 18068264
[  249.821105] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  249.821472] mmcblk0: error -84 transferring data
[  249.826202] end_request: I/O error, dev mmcblk0, sector 18068432
[  249.832244] end_request: I/O error, dev mmcblk0, sector 18068440
[  249.838287] end_request: I/O error, dev mmcblk0, sector 18068448
[  249.844329] end_request: I/O error, dev mmcblk0, sector 18068456
[  249.850372] end_request: I/O error, dev mmcblk0, sector 18068464
[  249.856414] end_request: I/O error, dev mmcblk0, sector 18068472
[  249.862457] end_request: I/O error, dev mmcblk0, sector 18068480
[  249.868499] end_request: I/O error, dev mmcblk0, sector 18068488
[  249.874542] end_request: I/O error, dev mmcblk0, sector 18068496
[  249.880584] end_request: I/O error, dev mmcblk0, sector 18068504
[  249.886627] end_request: I/O error, dev mmcblk0, sector 18068512
[  249.892669] end_request: I/O error, dev mmcblk0, sector 18068520
[  249.898712] end_request: I/O error, dev mmcblk0, sector 18068528
[  249.904754] end_request: I/O error, dev mmcblk0, sector 18068536
[  249.910766] end_request: I/O error, dev mmcblk0, sector 18068544
[  249.916809] end_request: I/O error, dev mmcblk0, sector 18068552
[  249.924377] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  249.924774] mmcblk0: error -84 transferring data
[  249.929443] end_request: I/O error, dev mmcblk0, sector 18068560
[  249.935516] end_request: I/O error, dev mmcblk0, sector 18068568
[  249.941558] end_request: I/O error, dev mmcblk0, sector 18068576
[  249.947601] end_request: I/O error, dev mmcblk0, sector 18068584
[  249.953643] end_request: I/O error, dev mmcblk0, sector 18068592
[  249.959686] end_request: I/O error, dev mmcblk0, sector 18068600
[  249.965728] end_request: I/O error, dev mmcblk0, sector 18068608
[  249.971740] end_request: I/O error, dev mmcblk0, sector 18068616
[  249.977783] end_request: I/O error, dev mmcblk0, sector 18068624
[  249.983825] end_request: I/O error, dev mmcblk0, sector 18068632
[  249.989868] end_request: I/O error, dev mmcblk0, sector 18068640
[  249.995910] end_request: I/O error, dev mmcblk0, sector 18068648
[  250.001953] end_request: I/O error, dev mmcblk0, sector 18068656
[  250.007995] end_request: I/O error, dev mmcblk0, sector 18068664
[  250.014038] end_request: I/O error, dev mmcblk0, sector 18068672
[  250.020080] end_request: I/O error, dev mmcblk0, sector 18068680
[  250.066436] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.066802] mmcblk0: error -84 transferring data
[  250.071502] end_request: I/O error, dev mmcblk0, sector 18068944
[  250.077545] end_request: I/O error, dev mmcblk0, sector 18068952
[  250.083587] end_request: I/O error, dev mmcblk0, sector 18068960
[  250.089630] end_request: I/O error, dev mmcblk0, sector 18068968
[  250.095672] end_request: I/O error, dev mmcblk0, sector 18068976
[  250.101715] end_request: I/O error, dev mmcblk0, sector 18068984
[  250.107757] end_request: I/O error, dev mmcblk0, sector 18068992
[  250.113800] end_request: I/O error, dev mmcblk0, sector 18069000
[  250.119842] end_request: I/O error, dev mmcblk0, sector 18069008
[  250.125885] end_request: I/O error, dev mmcblk0, sector 18069016
[  250.131927] end_request: I/O error, dev mmcblk0, sector 18069024
[  250.137969] end_request: I/O error, dev mmcblk0, sector 18069032
[  250.144012] end_request: I/O error, dev mmcblk0, sector 18069040
[  250.150054] end_request: I/O error, dev mmcblk0, sector 18069048
[  250.156097] end_request: I/O error, dev mmcblk0, sector 18069056
[  250.162109] end_request: I/O error, dev mmcblk0, sector 18069064
[  250.171997] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.172393] mmcblk0: error -84 transferring data
[  250.177124] end_request: I/O error, dev mmcblk0, sector 18069072
[  250.183166] end_request: I/O error, dev mmcblk0, sector 18069080
[  250.189208] end_request: I/O error, dev mmcblk0, sector 18069088
[  250.195251] end_request: I/O error, dev mmcblk0, sector 18069096
[  250.201293] end_request: I/O error, dev mmcblk0, sector 18069104
[  250.207336] end_request: I/O error, dev mmcblk0, sector 18069112
[  250.213378] end_request: I/O error, dev mmcblk0, sector 18069120
[  250.219421] end_request: I/O error, dev mmcblk0, sector 18069128
[  250.225463] end_request: I/O error, dev mmcblk0, sector 18069136
[  250.231506] end_request: I/O error, dev mmcblk0, sector 18069144
[  250.237548] end_request: I/O error, dev mmcblk0, sector 18069152
[  250.243591] end_request: I/O error, dev mmcblk0, sector 18069160
[  250.249633] end_request: I/O error, dev mmcblk0, sector 18069168
[  250.255676] end_request: I/O error, dev mmcblk0, sector 18069176
[  250.261718] end_request: I/O error, dev mmcblk0, sector 18069184
[  250.267761] end_request: I/O error, dev mmcblk0, sector 18069192
[  250.284851] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.284942] mmcblk0: error -84 transferring data
[  250.289611] end_request: I/O error, dev mmcblk0, sector 18068464
[  250.355560] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.356750] mmcblk0: error -84 transferring data
[  250.361541] end_request: I/O error, dev mmcblk0, sector 18069584
[  250.367584] end_request: I/O error, dev mmcblk0, sector 18069592
[  250.373626] end_request: I/O error, dev mmcblk0, sector 18069600
[  250.379669] end_request: I/O error, dev mmcblk0, sector 18069608
[  250.385711] end_request: I/O error, dev mmcblk0, sector 18069616
[  250.391754] end_request: I/O error, dev mmcblk0, sector 18069624
[  250.397796] end_request: I/O error, dev mmcblk0, sector 18069632
[  250.403839] end_request: I/O error, dev mmcblk0, sector 18069640
[  250.409881] end_request: I/O error, dev mmcblk0, sector 18069648
[  250.415924] end_request: I/O error, dev mmcblk0, sector 18069656
[  250.421966] end_request: I/O error, dev mmcblk0, sector 18069664
[  250.428009] end_request: I/O error, dev mmcblk0, sector 18069672
[  250.434051] end_request: I/O error, dev mmcblk0, sector 18069680
[  250.440063] end_request: I/O error, dev mmcblk0, sector 18069688
[  250.446105] end_request: I/O error, dev mmcblk0, sector 18069696
[  250.452148] end_request: I/O error, dev mmcblk0, sector 18069704
[  250.463592] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.463684] mmcblk0: error -84 transferring data
[  250.468353] end_request: I/O error, dev mmcblk0, sector 18069592
[  250.518005] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.518371] mmcblk0: error -84 transferring data
[  250.523010] end_request: I/O error, dev mmcblk0, sector 18070288
[  250.529083] end_request: I/O error, dev mmcblk0, sector 18070296
[  250.535125] end_request: I/O error, dev mmcblk0, sector 18070304
[  250.541168] end_request: I/O error, dev mmcblk0, sector 18070312
[  250.547210] end_request: I/O error, dev mmcblk0, sector 18070320
[  250.553253] end_request: I/O error, dev mmcblk0, sector 18070328
[  250.559295] end_request: I/O error, dev mmcblk0, sector 18070336
[  250.565338] end_request: I/O error, dev mmcblk0, sector 18070344
[  250.602539] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.602752] mmcblk0: error -84 transferring data
[  250.607513] end_request: I/O error, dev mmcblk0, sector 18070640
[  250.613555] end_request: I/O error, dev mmcblk0, sector 18070648
[  250.619598] end_request: I/O error, dev mmcblk0, sector 18070656
[  250.625640] end_request: I/O error, dev mmcblk0, sector 18070664
[  250.631713] end_request: I/O error, dev mmcblk0, sector 18070672
[  250.637756] end_request: I/O error, dev mmcblk0, sector 18070680
[  250.643798] end_request: I/O error, dev mmcblk0, sector 18070688
[  250.649841] end_request: I/O error, dev mmcblk0, sector 18070696
[  250.669433] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.669647] mmcblk0: error -84 transferring data
[  250.674407] end_request: I/O error, dev mmcblk0, sector 18070736
[  250.680480] end_request: I/O error, dev mmcblk0, sector 18070744
[  250.686523] end_request: I/O error, dev mmcblk0, sector 18070752
[  250.692565] end_request: I/O error, dev mmcblk0, sector 18070760
[  250.698608] end_request: I/O error, dev mmcblk0, sector 18070768
[  250.704650] end_request: I/O error, dev mmcblk0, sector 18070776
[  250.710693] end_request: I/O error, dev mmcblk0, sector 18070784
[  250.716735] end_request: I/O error, dev mmcblk0, sector 18070792
[  250.769683] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.770416] mmcblk0: error -84 transferring data
[  250.775177] end_request: I/O error, dev mmcblk0, sector 18071536
[  250.781219] end_request: I/O error, dev mmcblk0, sector 18071544
[  250.787261] end_request: I/O error, dev mmcblk0, sector 18071552
[  250.793304] end_request: I/O error, dev mmcblk0, sector 18071560
[  250.799377] end_request: I/O error, dev mmcblk0, sector 18071568
[  250.805419] end_request: I/O error, dev mmcblk0, sector 18071576
[  250.811462] end_request: I/O error, dev mmcblk0, sector 18071584
[  250.817474] end_request: I/O error, dev mmcblk0, sector 18071592
[  250.846984] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[  250.847076] mmcblk0: error -84 transferring data
[  250.851745] end_request: I/O error, dev mmcblk0, sector 18071576
[  333.806396] mmc0: card b368 removed
[  333.960632] Buffer I/O error on device mmcblk0p1, logical block 0
[  333.966857] lost page write due to I/O error on mmcblk0p1
tusters_kasten:~$

 

[sebt3]

# The errors appear also with WiFi switched off.

maybe it all is related to wifi instability?

not sure

I think it is related to your SD in the first slot (where the IO errors are from). It realy sound like a dead/fake card.
I don't have these kind of problem (I've just tried to copy kdegames.pnd and got no problem at all)

 

[WizardStan]

maybe it all is related to wifi instability?

Doubtful

# The errors appear also with WiFi switched off.

edit: h34r:

 

[zapman]

maybe it all is related to wifi instability?

no, as you can read in my post above, the IO error happens also if WiFi is disabled.

 

[zapman]

rephrasing: maybe wifi issues are being caused by SD I/O errors?

if you want to talk about WiFi, pls open up a new thread. We'ld like to find out why there are IO errors under certain circumstances..


Edit:
I just tried another thing: I connected a HDD (with own power supply) to the USB port and copied a 200MB file without any problems from the 16GB SD card in slot 1. That worked well 3 times in a row.

I copied the same file to the 2nd SD card in slot 2 and got the IO error after ~30 MB of transfered data. So I don't think it's a dead/ fake card, assuming that the read-speed is the same for the HDD and slot2 copy procedure.

 

[sebt3]

@zapman : missed that ?

I think it is related to your SD in the first slot (where the IO errors are from). It realy sound like a dead/fake card.

You should try your card in the first slot in a PC and try to see if linux does also report these reading problems

 

[WizardStan]

rephrasing: maybe wifi issues are being caused by SD I/O errors?

if you want to talk about WiFi, pls open up a new thread. We'ld like to find out why there are IO errors under certain circumstances..

sorry

Or just use one of the dozen or so threads already discussing it

 

[zapman]

@zapman : missed that ?

I think it is related to your SD in the first slot (where the IO errors are from). It realy sound like a dead/fake card.

No I didn't miss it. That's why I copied the file from the SDcard, slot 1 (16Gb, producing the error), to the HDD via usb.

I did some more things, and it seems the problem is related to the card reader in slot 1, not the type of cards:

Testfile for all copy combos: pandora-rootfs.tar.bz2 (194.6 MB)

Source: Target:
Slot 1

 

[Pleng]

hmm ive had trouble copying from slot 1 to slot 2. I always assumed that it was because the card in slot 1 was faster than the one in slot 2. Don't have my Pandora handy right now; have you tried swapping the cards around? Is it still slot 1 ---> slot 2 that's having the problem?

could be time for a bug report?

 

[WizardStan]

Edit:
I just tried another thing: I connected a HDD (with own power supply) to the USB port and copied a 200MB file without any problems from the 16GB SD card in slot 1. That worked well 3 times in a row.

I copied the same file to the 2nd SD card in slot 2 and got the IO error after ~30 MB of transfered data. So I don't think it's a dead/ fake card, assuming that the read-speed is the same for the HDD and slot2 copy procedure.

So you've got card 1 in slot 1, card 2 in slot 2, and HDD on the USB.
Copy from card 1 in slot 1 to HDD on USB is successful
Copy from card 1 in slot 1 to card 2 in slot 2 fails.
We need some more tests:
copy from card 1 in slot 2 to HDD on the USB : If this fails, then there's possibly a problem with slot 2
copy from HDD to card 2 in slot 2 : if this fails, it could be either slot or card
copy from HDD to card 2 in slot 1 : if this fails, it's almost definitely a problem with card 2
copy from card 2 in slot 1 to HDD \
copy from card 2 in slot 2 to HDD : These two tests, combined with the above, should prove conclusively if there's a problem with the Pandora or if it is actually card 2 that has a problem
copy from card 1 in slot 2 to card 2 in slot 1 : for completeness, but we should know if it's a problem with the card or not by this point

 

[zapman]

@zapman : missed that ?

I think it is related to your SD in the first slot (where the IO errors are from). It realy sound like a dead/fake card.

No I didn't miss it. That's why I copied the file from the SDcard, slot 1 (16Gb, producing the error), to the HDD via usb.


I tried some more things:

#####################################
Testfile for all copy combos: pandora-rootfs.tar.bz2 (194.6 MB)
SD cards used:
'16 GB': extrememory, SDHC 16GB, class 6
'32 GB': takeMS, SDHC, class 6
Each copy procedure was done at least 3 times in a row.

Source:___________Target:_________Result:
Slot 1, 16GB______Slot 2, 32GB____IO Error
Slot 1, 32GB______Slot 2, 16GB____IO Error

Slot 2, 32GB______Slot 1, 16GB____OK
Slot 2, 16GB______Slot 1, 32GB____OK

Slot 1, 32GB______HDD via USB_____OK
Slot 1, 16GB______HDD via USB_____OK
Slot 2, 16GB______HDD via USB_____OK
Slot 2, 32GB______HDD via USB_____OK
#####################################

So for me, it looks like the problem is NOT card specific and NOT due to a single problem with slot 1. Only when copying from slot 1 to slot 2, the error manifests.

EDIT:
doing

dd if=/dev/zero of=/media/<SDcard>/bla

works without any problems, for both slots. Also doing the diskdump on both slots at the same time is fine.

 

[neko]

Just tried this on my 64G SanDisk card and got zero errors, even under high CPU load.

Then I tried an old 16G Kingston card and it fails as Polossatik described.

So.. do I have a bad card, or is the Pandora slightly out of spec? It's possible that I got a fake card (I don't remember where this one came from).

 

[WizardStan]

So for me, it looks like the problem is NOT card specific and NOT due to a single problem with slot 1. Only when copying from slot 1 to slot 2, the error manifests itself.

The obvious work around then, for now, is to only copy things from slot 2 to slot 1.
Even so, it still does somehow appear related to the SD card, since some people report the error goes away using different cards. Always when copying from slot 1 to slot 2 it would seem though. Curious problem. I wish I had my own Pandora to experiment with.
Good sleuthing!

Edit to add:

So.. do I have a bad card, or is the Pandora slightly out of spec? It's possible that I got a fake card (I don't remember where this one came from).

Try copying from slot 2 to slot 1, see if you still get errors. Everyone that's reported errors has reported it failing when copying from slot 1 to slot 2.

 

[neko]

So.. do I have a bad card, or is the Pandora slightly out of spec? It's possible that I got a fake card (I don't remember where this one came from).

Try copying from slot 2 to slot 1, see if you still get errors. Everyone that's reported errors has reported it failing when copying from slot 1 to slot 2.

It failed in the read test using dd. It works until I launch another app and then gets read errors.

I switched the cards, putting the 64G card in slot 1 and the 16G card in slot 2. Now I get read errors on the 64G card and the 16G card is fine.

Apparently slot 1 is bad. I hope this is covered under warranty...

 

[zapman]

@zapman : missed that ?

I think it is related to your SD in the first slot (where the IO errors are from). It realy sound like a dead/fake card.

No I didn't miss it. That's why I copied the file from the SDcard, slot 1 (16Gb, producing the error), to the HDD via usb.


I tried some more things:

#####################################
Testfile for all copy combos: pandora-rootfs.tar.bz2 (194.6 MB)
SD cards used:
'16 GB': extrememory, SDHC 16GB, class 6
'32 GB': takeMS, SDHC, class 6
Each copy procedure was done at least 3 times in a row.

Source:___________Target:_________Result:
Slot 1, 16GB______Slot 2, 32GB____IO Error
Slot 1, 32GB______Slot 2, 16GB____IO Error

Slot 2, 32GB______Slot 1, 16GB____OK
Slot 2, 16GB______Slot 1, 32GB____OK

Slot 1, 32GB______HDD via USB_____OK
Slot 1, 16GB______HDD via USB_____OK
Slot 2, 16GB______HDD via USB_____OK
Slot 2, 32GB______HDD via USB_____OK
#####################################

So for me, it looks like the problem is NOT card specific and NOT due to a single problem with slot 1. Only when copying from slot 1 to slot 2, the error manifests.

EDIT:
doing

dd if=/dev/zero of=/media/<SDcard>/bla

works without any problems, for both slots. Also doing the diskdump on both slots at the same time is fine.

My girlfriend has a Pandora as well. I tried my SD cards with her Pandi and got the same results: copying from slot 1 to slot 2 does not work with big files. Afterwards I used her SD cards (4GB Sony and 32GB takeMS): same thing -> error!

 

[Pleng]

Apparently slot 1 is bad. I hope this is covered under warranty...

Whoa steady on there! It could well be a software issue as many people are experiencing it. In fact I'm almost certain this is software related. I'll file a bug report linking to this thread.

 

[tsh]

So, after 1 month of not observing any problems, I find that if I try to copy between slot1/slot2, then I get errors after 15-17MB. I can reliably md5sum the files, and copy to NAND. Just copied the file om my desktop, but that is a rather different scenario. Should try the card reader on my pandora, I guess.

This is quite likely a software issue, particularly if it is interrupt related. WiFi was off for my failures (experimental kernal had broken it)

If anyone can give me some pointers for low-level debugging this, I will have a look.
Edit: I re-mounted these cards, and now can copy to the EXT2 one, but not to the FAT one (so I think I need to re-format that one before knowing if there is a real problem)

 

[neko]

This is quite likely a software issue, particularly if it is interrupt related. WiFi was off for my failures (experimental kernal had broken it)

If anyone can give me some pointers for low-level debugging this, I will have a look.

Mine fails with only one SD card inserted in the left slot, doing "sudo dd if=/dev/mmcblk0 of=/dev/null bs=1048576", then launch another app. 500MHz, Wifi off.

Doing the same with a SD card in the right slot works okay.