I've been having issues with my Helios4 becoming unresponsive when it's been up for a while.

 

I decided to do some more thorough investigating and found that it was having problems writing to the sdcard. That led to the following entries in syslog:

 

Dec 20 21:36:43 helios-backup kernel: [318645.034243] mmc0: Timeout waiting for hardware interrupt.
Dec 20 21:36:43 helios-backup kernel: [318645.034254] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
Dec 20 21:36:43 helios-backup kernel: [318645.034258] mmc0: sdhci: Sys addr:  0x00000008 | Version:  0x00000202
Dec 20 21:36:43 helios-backup kernel: [318645.034263] mmc0: sdhci: Blk size:  0x00007200 | Blk cnt:  0x00000001
Dec 20 21:36:43 helios-backup kernel: [318645.034267] mmc0: sdhci: Argument:  0x0084a0d0 | Trn mode: 0x0000002b
Dec 20 21:36:43 helios-backup kernel: [318645.034271] mmc0: sdhci: Present:   0x01e60006 | Host ctl: 0x00000017
Dec 20 21:36:43 helios-backup kernel: [318645.034274] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000000
Dec 20 21:36:43 helios-backup kernel: [318645.034278] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x00000207
Dec 20 21:36:43 helios-backup kernel: [318645.034282] mmc0: sdhci: Timeout:   0x0000000e | Int stat: 0x00000000
Dec 20 21:36:43 helios-backup kernel: [318645.034285] mmc0: sdhci: Int enab:  0x03ff000b | Sig enab: 0x03ff000b
Dec 20 21:36:43 helios-backup kernel: [318645.034289] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
Dec 20 21:36:43 helios-backup kernel: [318645.034292] mmc0: sdhci: Caps:      0x25fcc8b2 | Caps_1:   0x00002f77
Dec 20 21:36:43 helios-backup kernel: [318645.034296] mmc0: sdhci: Cmd:       0x0000193a | Max curr: 0x00000000
Dec 20 21:36:43 helios-backup kernel: [318645.034299] mmc0: sdhci: Resp[0]:   0x00000900 | Resp[1]:  0x00000000
Dec 20 21:36:43 helios-backup kernel: [318645.034303] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000900
Dec 20 21:36:43 helios-backup kernel: [318645.034306] mmc0: sdhci: Host ctl2: 0x00000000
Dec 20 21:36:43 helios-backup kernel: [318645.034309] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x78275208
Dec 20 21:36:43 helios-backup kernel: [318645.034313] mmc0: sdhci: ============================================
Dec 20 21:36:46 helios-backup kernel: [318648.042018] mmc0: Card stuck being busy! __mmc_poll_for_busy
Dec 20 21:36:48 helios-backup kernel: [318649.277911] mmc0: card never left busy state
Dec 20 21:36:48 helios-backup kernel: [318649.277918] mmc0: tried to HW reset card, got error -110
Dec 20 21:36:48 helios-backup kernel: [318649.277923] mmcblk0: recovery failed!
Dec 20 21:36:48 helios-backup kernel: [318649.277947] blk_update_request: I/O error, dev mmcblk0, sector 8691920 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Dec 20 21:36:48 helios-backup kernel: [318649.277958] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:348: I/O error 10 writing to inode 382819 starting block 1086491)

 

Is it possible this is due to the power supply starting to go bad? I haven't yet tried using different sdcards, but that would be my next step.

 

Has anyone else seen this?

From the error messages I would expect it to be the card. 

 

I have a similar problem but mine is a worn out sd card slot, so I just boot from a different medium now.

I had a bunch of random issues - stuttering, freezes, issues while copying. It turned it out the issue was extreme amounts of dust on my unit. I disassembled it, thoroughly cleaned everything out - and that fixed my issue