Mmc error on just flashed board

I have an Apalis IMX6 IT v1.1B board with ixora carrier board.

I just installed “Apalis-iMX6_LXDE-Image 2.7.2 20170410” using Toradex easy installer and on boot and after bootup I receive the following error continuously. Could this be a hardware fault ?

Angstrom v2016.12 - Kernel 4.1.39-2.7.2+gba2f75f

Apalis-iMX6_LXDE-Image 2.7.2 20170410

apalis-imx6 login: [  201.474549] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control x
[  201.482273] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  206.112863] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  206.120550] mmcblk1: error -110 sending stop command, original cmd response 0x900, card status 0x0
[  206.130038] mmcblk1: error -110 transferring data, sector 60751744, nr 8, cmd response 0x900, car0
[  206.140072] mmcblk1: retrying using single block read
[  216.152859] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  216.160571] mmcblk1: error -110 transferring data, sector 60751744, nr 8, cmd response 0x900, car0
[  216.170572] blk_update_request: I/O error, dev mmcblk1, sector 60751744
[  226.192840] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  226.200550] mmcblk1: error -110 transferring data, sector 60751745, nr 7, cmd response 0x900, car0
[  226.210554] blk_update_request: I/O error, dev mmcblk1, sector 60751745
[  236.232857] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  236.240553] mmcblk1: error -110 transferring data, sector 60751746, nr 6, cmd response 0x900, car0
[  236.250548] blk_update_request: I/O error, dev mmcblk1, sector 60751746
[  246.272860] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  246.280551] mmcblk1: error -110 transferring data, sector 60751747, nr 5, cmd response 0x900, car0
[  246.290542] blk_update_request: I/O error, dev mmcblk1, sector 60751747
[  256.312853] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  256.320547] mmcblk1: error -110 transferring data, sector 60751748, nr 4, cmd response 0x900, car0
[  256.330543] blk_update_request: I/O error, dev mmcblk1, sector 60751748
[  266.353917] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  266.361592] mmcblk1: error -110 transferring data, sector 60751749, nr 3, cmd response 0x900, car0
[  266.371584] blk_update_request: I/O error, dev mmcblk1, sector 60751749
[  276.399266] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  276.406966] mmcblk1: error -110 transferring data, sector 60751750, nr 2, cmd response 0x900, car0
[  276.416961] blk_update_request: I/O error, dev mmcblk1, sector 60751750
[  286.442064] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  286.449750] mmcblk1: error -110 transferring data, sector 60751751, nr 1, cmd response 0x900, car0
[  286.459738] blk_update_request: I/O error, dev mmcblk1, sector 60751751
[  296.483543] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  296.491251] mmcblk1: error -110 sending stop command, original cmd response 0x900, card status 0x0
[  296.500733] mmcblk1: error -110 transferring data, sector 60751744, nr 8, cmd response 0x900, car0
[  296.510762] mmcblk1: retrying using single block read
[  306.524292] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  306.531955] mmcblk1: error -110 transferring data, sector 60751744, nr 8, cmd response 0x900, car0
[  306.541982] blk_update_request: I/O error, dev mmcblk1, sector 60751744
[  316.564703] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  316.572944] mmcblk1: error -110 transferring data, sector 60751745, nr 7, cmd response 0x900, car0
[  316.582945] blk_update_request: I/O error, dev mmcblk1, sector 60751745
[  326.604912] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  326.613229] mmcblk1: error -110 transferring data, sector 60751746, nr 6, cmd response 0x900, car0
[  326.623224] blk_update_request: I/O error, dev mmcblk1, sector 60751746
[  336.642440] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  336.650697] mmcblk1: error -110 transferring data, sector 60751747, nr 5, cmd response 0x900, car0
[  336.660690] blk_update_request: I/O error, dev mmcblk1, sector 60751747
[  346.679882] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  346.688107] mmcblk1: error -110 transferring data, sector 60751748, nr 4, cmd response 0x900, car0
[  346.698111] blk_update_request: I/O error, dev mmcblk1, sector 60751748
[  356.717879] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  356.726006] mmcblk1: error -110 transferring data, sector 60751749, nr 3, cmd response 0x900, car0
[  356.736001] blk_update_request: I/O error, dev mmcblk1, sector 60751749
[  366.756360] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  366.764733] mmcblk1: error -110 transferring data, sector 60751750, nr 2, cmd response 0x900, car0
[  366.774731] blk_update_request: I/O error, dev mmcblk1, sector 60751750
[  376.795120] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[  376.803289] mmcblk1: error -110 transferring data, sector 60751751, nr 1, cmd response 0x900, car0
[  376.813285] blk_update_request: I/O error, dev mmcblk1, sector 60751751
[  376.819994] Buffer I/O error on dev mmcblk1, logical block 7593968, async page read
[   72.372892] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[   72.395412] mmcblk1: error -110 transferring data, sector 4, nr 4, cmd response 0x900, card statu0
[   72.419790] blk_update_request: I/O error, dev mmcblk1, sector 4
[   82.452888] mmc1: Timeout waiting for hardware interrupt. retries left=0 opcode=0
[   82.475514] mmcblk1: error -110 transferring data, sector 5, nr 3, cmd response 0x900, card statu0
[   82.499938] blk_update_request: I/O error, dev mmcblk1, sector 5

What you are seeing is probably an issue with the SD card as mmc0 is what the eMMC of our module is usually running at:

[    1.510717] sdhci: Secure Digital Host Controller Interface driver
[    1.510720] sdhci: Copyright(c) Pierre Ossman
[    1.510730] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.511784] /soc/aips-bus@02100000/usdhc@02190000: voltage-ranges unspecified
[    1.511811] sdhci-esdhc-imx 2190000.usdhc: Got CD GPIO
[    1.513223] sdhci-esdhc-imx 2190000.usdhc: No vqmmc regulator found
[    1.552847] mmc1: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
[    1.553265] /soc/aips-bus@02100000/usdhc@02194000: voltage-ranges unspecified
[    1.553291] sdhci-esdhc-imx 2194000.usdhc: Got CD GPIO
[    1.554625] sdhci-esdhc-imx 2194000.usdhc: No vqmmc regulator found
[    1.602864] mmc2: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
[    1.603447] /soc/aips-bus@02100000/usdhc@02198000: voltage-ranges unspecified
[    1.603808] sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found
[    1.642724] mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
[    1.988824] mmc0: MAN_BKOPS_EN bit is not set
[    2.119008] mmc0: new DDR MMC card at address 0001
[    2.119388] mmcblk0: mmc0:0001 004GE0 3.69 GiB
[    2.119497] mmcblk0boot0: mmc0:0001 004GE0 partition 1 2.00 MiB
[    2.119607] mmcblk0boot1: mmc0:0001 004GE0 partition 2 2.00 MiB
[    2.127850]  mmcblk0: p1 p2

And this are the parameters as reported by the Linux kernel:

root@apalis-imx6:~# cat /sys/kernel/debug/mmc0/ios 
clock:          52000000 Hz
actual clock:   49500000 Hz
vdd:            21 (3.3 ~ 3.4 V)
bus mode:       2 (push-pull)
chip select:    0 (don't care)
power mode:     2 (on)
bus width:      3 (8 bits)
timing spec:    8 (mmc DDR52)
signal voltage: 0 (3.30 V)

Could you try once without the SD card, re-seating the SD card or using a different brand/model SD card and see what happens?