Error: sd-card ejects with read failures

Enzephalopat
 
Posts: 5
Joined: Sat Jan 07, 2017 7:00 pm

Error: sd-card ejects with read failures

Wed Jan 11, 2017 2:33 pm

Hi,

I tried to attach sd-cards to my Vocore2 Ultimate (firmware 2016.12.24) and got some strange behavior. After plugging in the sd-card, I get a sequence of repeating messages in dmesg saying that the sd-card is removed and re-attached due to read failures. I tried two different sd-cards (SanDisk Ultra 8 GB SDHC and 32 GB SDHC), with different partitions (one or two partitions on it, formatted with either VFAT or EXT4), and all of them are read properly in different other setups (in an sd-card-reader or in a Beaglebone board).

Following are two examples of the never-ending sequence of error messages:

Code: Select all
[  279.580000] mmc0: new high speed SDHC card at address e624
[  279.580000] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[  279.600000]  mmcblk0: p1 p2
[  281.670000] msdc-1 -> cmd<18> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.680000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.690000] mmcblk0: error -159 sending status command, retrying
[  281.700000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.710000] mmcblk0: error -159 sending status command, retrying
[  281.710000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.720000] mmcblk0: error -159 sending status command, aborting
[  281.730000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.740000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.750000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.760000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6ad>
[  281.770000] mmc0: card e624 removed
[  282.930000] mmc0: new high speed SDHC card at address e624
[  282.930000] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[  282.950000]  mmcblk0: p1 p2
[  285.370000] FAT-fs (mmcblk0p1): Directory bread(block 2256) failed
[  285.380000] EXT4-fs warning (device mmcblk0p2): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  286.420000] FAT-fs (mmcblk0p1): Directory bread(block 2256) failed
[  286.430000] EXT4-fs warning (device mmcblk0p2): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  287.470000] FAT-fs (mmcblk0p1): Directory bread(block 2256) failed
[  287.480000] EXT4-fs warning (device mmcblk0p2): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  288.010000] msdc-1 -> cmd<18> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.020000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.030000] mmcblk0: error -159 sending status command, retrying
[  288.030000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.040000] mmcblk0: error -159 sending status command, retrying
[  288.050000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.060000] mmcblk0: error -159 sending status command, aborting
[  288.060000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.070000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.080000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.090000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x6c9>
[  288.100000] mmc0: card e624 removed
[  289.240000] mmc0: new high speed SDHC card at address e624
[  289.260000] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[  289.260000]  mmcblk0: p1 p2
[  293.250000] FAT-fs (mmcblk0p1): Directory bread(block 2256) failed
[  293.250000] EXT4-fs warning (device mmcblk0p2): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  293.470000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  293.470000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  293.480000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  293.490000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  293.500000] mmc0: card e624 removed
[  294.300000] FAT-fs (mmcblk0p1): Directory bread(block 2256) failed
[  294.300000] EXT4-fs warning (device mmcblk0p2): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  294.630000] mmc0: new high speed SDHC card at address e624
[  294.630000] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[  294.640000]  mmcblk0: p1 p2
[  295.350000] FAT-fs (mmcblk0p1): Directory bread(block 2256) failed
[  295.350000] EXT4-fs warning (device mmcblk0p2): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  295.870000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  295.870000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  295.880000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  295.890000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  295.900000] mmc0: card e624 removed
[  297.070000] mmc0: new high speed SDHC card at address e624
[  297.070000] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[  297.100000]  mmcblk0: p1 p2


Code: Select all
[  118.760000] mmcblk0: mmc0:0007 SL32G 28.9 GiB
[  118.770000]  mmcblk0: p1
[  119.530000] EXT4-fs (mmcblk0p1): recovery complete
[  119.550000] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts:
[  120.970000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  120.970000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  120.980000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  120.990000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  121.000000] mmc0: card 0007 removed
[  122.100000] mmc0: new high speed SDHC card at address 0007
[  122.110000] mmcblk0: mmc0:0007 SL32G 28.9 GiB
[  122.120000]  mmcblk0: p1
[  123.160000] EXT4-fs warning (device mmcblk0p1): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  124.200000] EXT4-fs warning (device mmcblk0p1): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  126.260000] msdc-1 -> cmd<18> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.270000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.280000] mmcblk0: error -159 sending status command, retrying
[  126.290000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.300000] mmcblk0: error -159 sending status command, retrying
[  126.300000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.310000] mmcblk0: error -159 sending status command, aborting
[  126.320000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.330000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.340000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.340000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0x66b>
[  126.350000] mmc0: card 0007 removed
[  127.440000] mmc0: new high speed SDHC card at address 0007
[  127.450000] mmcblk0: mmc0:0007 SL32G 28.9 GiB
[  127.460000]  mmcblk0: p1
[  128.060000] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.
[  128.060000] Aborting journal on device mmcblk0p1-8.
[  128.070000] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.
[  128.400000] EXT4-fs warning (device mmcblk0p1): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  129.440000] EXT4-fs warning (device mmcblk0p1): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  130.660000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  130.660000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  130.670000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  130.680000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0x8>
[  130.690000] mmc0: card 0007 removed
[  132.770000] mmc0: new high speed SDHC card at address 0007
[  132.780000] mmcblk0: mmc0:0007 SL32G 28.9 GiB
[  132.790000]  mmcblk0: p1
[  133.530000] EXT4-fs warning (device mmcblk0p1): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  134.570000] EXT4-fs warning (device mmcblk0p1): __ext4_read_dirblock:884: error -5 reading directory block (ino)
[  134.990000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:3><0x656>
[  134.990000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:3><0x656>
[  135.000000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:3><0x656>
[  135.010000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:3><0x656>
[  135.020000] mmc0: card 0007 removed
[  136.130000] mmc0: new high speed SDHC card at address 0007
[  136.140000] mmcblk0: mmc0:0007 SL32G 28.9 GiB
[  136.150000]  mmcblk0: p1


Can anybody help to get the sd-cards working?

Vonger
 
Posts: 675
Joined: Sun Oct 19, 2014 6:00 am

Re: Error: sd-card ejects with read failures

Wed Jan 11, 2017 4:27 pm

Weird, first time read this issue

Enzephalopat
 
Posts: 5
Joined: Sat Jan 07, 2017 7:00 pm

Re: Error: sd-card ejects with read failures

Thu Jan 12, 2017 6:37 pm

Yes, this is kind of weird. Usually the sd-cards fail with this error already while booting up.
However, I observed that the sd-cards work on rare occasions (i.e., the sd-card auto mounts and I can read the contents and write to a text file properly). However, this does not last for long and usually after a couple of seconds or even one minte I get the aforementioned errors. Once I am in the error state I didn't manage to recover so far even with plugging out and plugging in the sd-card several times or even waiting for an hour our so before re-plugging the card. I can only recover (on rare occasions) after cutting the power.

I'd really like to find out whether this is a hardware error or a software error. Any suggestions?

Enzephalopat
 
Posts: 5
Joined: Sat Jan 07, 2017 7:00 pm

Re: Error: sd-card ejects with read failures

Thu Jan 12, 2017 6:45 pm

As a side note: I hat to remove the shell on the USB-port side before being able to plug in the sd-card because the cut-out for the sc-card was not in the right place. It should have been shifted slightly towards the power-in-port in order to match the location of the reader underneath. On my VoCore2 Ultimate, I extended the cut-out using a knife which enabled me to insert sd-cards also with the shell completely mounted.

Enzephalopat
 
Posts: 5
Joined: Sat Jan 07, 2017 7:00 pm

Re: Error: sd-card ejects with read failures

Sat Jan 21, 2017 8:08 am

Ping :-)

Reading from and writing to SD-cards usually works directly after cold start. It works sometimes for about one minute before the aforementioned error comes up. USB mass storage works properly, though. Any suggestions what could be causing this? Which sd-cards are known to work?
I also tried the LEDE firmware (https://lede-project.org/toh/hwdata/voc ... re_vocore2), however, the sd-card does not get detected at all there (dmesg does not tell anything when inserting the sd-card).

Cheers,
Enze

Vonger
 
Posts: 675
Joined: Sun Oct 19, 2014 6:00 am

Re: Error: sd-card ejects with read failures

Wed Feb 01, 2017 2:21 pm

I guess this is the wireless crosstalk to the SD card. It is possible to be strong EMC(electromagnetic interference)
That should not happen. You can try to call "wifi off" or disable wireless from /etc/config/wireless, reboot and connect again, check if that happen again.

level6
 
Posts: 1
Joined: Mon Feb 06, 2017 6:26 am

Re: Error: sd-card ejects with read failures

Mon Feb 06, 2017 6:36 am

I get the same behavior.

It seemed to work fine until I overlay'ed a partition of the card. Strangely, now, even if I disable my overlay, the mounted partition behaves this way. I suppose that just means that I got lucky or didn't use it enough before I overlay'ed, but I mention it in case it is a possible clue.

I developed something on RPi a while back in which I experienced similar issues. While I cannot find the information regarding it to show to you, it came down to some locking/timing issues in a buggy driver in Debian (Raspbian). I also seem to remember that faster sdcards amplified the behavior.

The card will remount itself in ro mode and it's nearly impossible to bring back out of that mode.

I have tried the sdcards that worked in my other project, and that doesn't help.

While I doubt that disabling the radio will help, I could give this a try for you, tomorrow, if no one beats me to it.

As I was typing this:

Code: Select all
root@OpenWrt:/# ls -al
[21016.350000] EXT4-fs warning (device mmcblk0p1): __ext4_read_dirblock:884: error -5 reading directory block (ino 1046529, block 0)
root@OpenWrt:/# [21608.790000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:2><0xe7d>
[21608.790000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:2><0xe7d>
[21608.800000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:2><0xe7d>
[21608.810000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:2><0xe7d>
[21608.820000] mmc0: card 0007 removed
[21608.900000] mmc0: new high speed SDHC card at address 0007
[21608.910000] mmcblk: probe of mmc0:0007 failed with error -28
[21759.120000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0xe8e>
[21759.120000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0xe8e>
[21759.130000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0xe8e>
[21759.140000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<kworker/u2:1><0xe8e>
[21759.150000] mmc0: card 0007 removed
[21760.230000] mmc0: new high speed SDHC card at address 0007
[21760.240000] mmcblk: probe of mmc0:0007 failed with error -28


If there is any debugging available which you would like me to bump up, let me know. I have this unit remote logging to a server. We can send as much noise as you like. :)

Vonger
 
Posts: 675
Joined: Sun Oct 19, 2014 6:00 am

Re: Error: sd-card ejects with read failures

Wed Feb 08, 2017 9:55 am

I think I find the problem. It is not crosstalk and not software issue.
Just TF card slot, can not well connect for some TF card. if data line can not touch card, it will report the weird issue.

sholdowa
 
Posts: 1
Joined: Fri Feb 17, 2017 10:15 pm

Re: Error: sd-card ejects with read failures

Fri Feb 17, 2017 10:17 pm

I'm having similar problems with a vocore2...

Code: Select all
[  808.030000] msdc-1 -> cmd<18> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.040000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.050000] mmcblk0: error -159 sending status command, retrying
[  808.050000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.060000] mmcblk0: error -159 sending status command, retrying
[  808.070000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.080000] mmcblk0: error -159 sending status command, aborting
[  808.080000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.090000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.100000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.110000] msdc-1 -> cmd<13> card<0> power<2> <- msdc_ops_request() : L<2120> PID<mmcqd/0><0xb90>
[  808.120000] mmc0: card 1234 removed
[  809.200000] mmc0: new high speed SDHC card at address 1234
[  809.210000] mmcblk mmc0:1234: no of_node; not parsing pinctrl DT
[  809.220000] mmcblk0: mmc0:1234 SA32G 28.9 GiB
[  809.220000]  mmcblk0: p1
[  812.180000] fat__get_entry: 118 callbacks suppressed
[  812.190000] FAT-fs (mmcblk0p1): Directory bread(block 16384) failed
[  812.190000] FAT-fs (mmcblk0p1): Directory bread(block 16385) failed
[  812.200000] FAT-fs (mmcblk0p1): Directory bread(block 16386) failed
[  812.210000] FAT-fs (mmcblk0p1): Directory bread(block 16387) failed
[  812.210000] FAT-fs (mmcblk0p1): Directory bread(block 16388) failed
[  812.220000] FAT-fs (mmcblk0p1): Directory bread(block 16389) failed
[  812.230000] FAT-fs (mmcblk0p1): Directory bread(block 16390) failed
[  812.230000] FAT-fs (mmcblk0p1): Directory bread(block 16391) failed
[  812.240000] FAT-fs (mmcblk0p1): Directory bread(block 16392) failed
[  812.250000] FAT-fs (mmcblk0p1): Directory bread(block 16393) failed


Anyone got any ideas?

xtejkl
 
Posts: 1
Joined: Tue Dec 12, 2017 9:06 am

Re: Error: sd-card ejects with read failures

Tue Dec 12, 2017 9:19 am

We are observing the same issue with the SD card. We discovered that this beahvioral is temperature sensitive. It is enough to cool the CPU by several degrees and the SD card works. But the same behavioral can be seen when heating working device above 70 degree. Than the SD card is lost. It looks as there are some dependencies in the impedance matching circuit for SD interface (five 10 kOhm resistors). It may help to decrease their value little bit.

Next
Return to VoCore2/Lite/Ultimate

Who is online

Users browsing this forum: No registered users and 5 guests