Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
New Contributor I
1,585 Views

Edison error

I was working on the Intel Edison and all of a sudden it stopped working and started giving out the following error

root@edison:~# [ 608.646597] mmc0: cache flush error -110

[ 608.650831] end_request: I/O error, dev mmcblk0, sector 0

[ 618.670182] mmc0: Timeout waiting for hardware interrupt.

[ 618.670256] mmc0: dump APIC RTE reg - L32: 0x00008982, H32: 0x03000000

[ 618.687061] mmcblk0: error -110 sending status command, retrying

[ 618.694302] mmcblk0: error -110 sending status command, retrying

[ 618.701580] mmcblk0: error -110 sending status command, aborting

[ 618.701665] end_request: I/O error, dev mmcblk0, sector 2998272

[ 618.701735] Buffer I/O error on device mmcblk0p8, logical block 358400

[ 628.708890] mmc0: Timeout waiting for hardware interrupt.

[ 628.708964] mmc0: dump APIC RTE reg - L32: 0x00008982, H32: 0x03000000

[ 628.725742] mmcblk0: error -110 sending status command, retrying

[ 628.732965] mmcblk0: error -110 sending status command, retrying

[ 628.740157] mmcblk0: error -110 sending status command, aborting

[ 628.740240] end_request: I/O error, dev mmcblk0, sector 656072

[ 628.740317] end_request: I/O error, dev mmcblk0, sector 656080

[ 628.740564] Aborting journal on device mmcblk0p8-8.

[ 628.740731] EXT4-fs error (device mmcblk0p8) in ext4_reserve_inode_write:4962: Journal has aborted

[ 638.767433] mmc0: Timeout waiting for hardware interrupt.

[ 638.767505] mmc0: dump APIC RTE reg - L32: 0x00008982, H32: 0x03000000

[ 638.772568] mmcblk0: error -110 sending status command, retrying

[ 638.787177] mmcblk0: error -110 sending status command, retrying

[ 638.788552] mmcblk0: error -110 sending status command, aborting

[ 638.788624] end_request: I/O error, dev mmcblk0, sector 655360

[ 638.788692] Buffer I/O error on device mmcblk0p8, logical block 65536

[ 638.811847] JBD2: Error -5 detected when updating journal superblock for mmcblk0p8-8.

[ 648.806086] mmc0: Timeout waiting for hardware interrupt.

[ 648.806159] mmc0: dump APIC RTE reg - L32: 0x00008982, H32: 0x03000000

[ 648.822931] mmcblk0: error -110 sending status command, retrying

[ 648.830132] mmcblk0: error -110 sending status command, retrying

[ 648.837363] mmcblk0: error -110 sending status command, aborting

[ 648.837446] end_request: I/O error, dev mmcblk0, sector 131072

[ 648.837515] Buffer I/O error on device mmcblk0p8, logical block 0

[ 648.837748] EXT4-fs error (device mmcblk0p8) in ext4_dirty_inode:5081: Journal has aborted

[ 648.837850] EXT4-fs (mmcblk0p8): previous I/O error to superblock detected

[ 658.884377] mmc0: Timeout waiting for hardware interrupt.

[ 658.884447] mmc0: dump APIC RTE reg - L32: 0x00008982, H32: 0x03000000

[ 658.902125] mmcblk0: error -110 sending status command, retrying

[ 658.903538] mmcblk0: error -110 sending status command, retrying

[ 658.914087] mmcblk0: error -110 sending status command, aborting

[ 658.920091] end_request: I/O error, dev mmcblk0, sector 131072

[ 658.925917] Buffer I/O error on device mmcblk0p8, logical block 0

[ 658.926109] EXT4-fs (mmcblk0p8): previous I/O error to superblock detected

[ 668.943275] mmc0: Timeout waiting for hardware interrupt.

[ 668.943348] mmc0: dump APIC RTE reg - L32: 0x00008982, H32: 0x03000000

[ 668.960342] mmcblk0: error -110 sending status command, retrying

[ 668.961868] mmcblk0: error -110 sending status command, retrying

[ 668.972300] mmcblk0: error -110 sending status command, aborting

[ 668.972386] end_request: I/O error, dev mmcblk0, sector 131072

[ 668.972454] Buffer I/O error on device mmcblk0p8, logical block 0

[ 668.972641] EXT4-fs error (device mmcblk0p8): __ext4_journal_start_sb:62: Detected aborted journal

[ 668.972765] EXT4-fs (mmcblk0p8): Remounting filesystem read-only

[ 668.972833] EXT4-fs (mmcblk0p8): previous I/O error to superblock detected

[ 679.021911] mmc0: Timeout waiting for hardware interrupt.

[ 679.021983] mmc0: dump APIC RTE reg - L32: 0x00008982, H32: 0x03000000

[ 679.038896] mmcblk0: error -110 sending status command, retrying

[ 679.043311] mmcblk0: error -110 sending status command, retrying

[ 679.052159] mmcblk0: error -110 sending status command, aborting

[ 679.052236] end_request: I/O error, dev mmcblk0, sector 131072

[ 679.052303] Buffer I/O error on device mmcblk0p8, logical block 0

[ 679.052508] EXT4-fs (mmcblk0p8): ext4_da_writepages: jbd2_start: 2147483647 pages, ino 27302; err -30

After that I unplugged the power and plugged it back on the mini USB jack. since then the ds3 led light has been blinking continuously without stopping and the Intel Edison is not booting up as well. Any idea what I can do to eliminate this error from happening? I am in the middle of a design project and it is too late for me to change to another MCU.

3 Replies
Highlighted
Employee
14 Views

Hi dunex_1,

Have you tried flashing your module? I would suggest you to try with this /docs/DOC-98643 https://communities.intel.com/docs/DOC-98643. There you'll find two different methods, one that uses the Flash Tool Lite and the alternative method, you'll find instructions for both on that document.

Please let us know your results, hopefully the image just got corrupted and this will be enough to recover it.

Regards,

Pablo

Highlighted
New Contributor I
14 Views

Hi PabloM_Intel

I cannot see the Intel Edison drive on my computer for me to be able to flash it using one of the flashing tools. The ds3 Led light is blinking so fast continuously. If there is anything else I can try please let me know.

Thanks,

Chinedu.

0 Kudos
Highlighted
Employee
14 Views

Hi dunex_1,

This seems like a warranty issue. Could you please open a ticket following this link, https://customercare.intel.com/?lang=en-US https://customercare.intel.com/?lang=en-US? We'll continue helping you there, we just need to determine if the Edison module is indeed damaged.

Regards,

Pablo

0 Kudos