10-19-2017, 10:16 AM
...A small update:
Over the last days, I kept an eye on this issue, restarted the Rock64 several times, let it sit idle, ran some tasks, then idling again...
All I found was:
The last two days, the Rock64 was just idling on my desk, while I was out of town, an this is what I came back to:
Again, nothing out of the ordinary. The EXT4-fs comments, 300s after boot and then daily afterwards, are well known. One error while idling for two days. That's near okay.
Then, I did some tinkering (copying files, repeatedly loading/exiting ipython):
...And there we are again. The r/w speed while copying files is okay-ish, I guess: Using rsync (I have no idea whether this is appropriate for benchmarking) I get +50MB/s. As source and target device are both mmcblk0, I do not expect any world record values. But, being used to class4 SD cards, I am quite happy.
The only thing that bothers me, is my fear of the eMMC dying or corrupting. It would make me more than happy, if someone could be as kind as to explain to me what's going on with those errors.
Thanks, -ac
Over the last days, I kept an eye on this issue, restarted the Rock64 several times, let it sit idle, ran some tasks, then idling again...
All I found was:
- Doing tasks that access flash (e.g. loading programs) triggers errors.
- Doing cpu-bound tasks (e.g. some lightweight linear algebra in iPython) creates very few errors.
- Error distribution over time fluctuates heavily (some boot-ups without any errors, on other occasions the log is bursting with errors).
The last two days, the Rock64 was just idling on my desk, while I was out of town, an this is what I came back to:
Code:
[ 305.218470] EXT4-fs (mmcblk0p7): error count since last fsck: 5
[ 305.218553] EXT4-fs (mmcblk0p7): initial error at time 4: ext4_journal_check_start:56
[ 305.218592] EXT4-fs (mmcblk0p7): last error at time 1507828026: ext4_find_entry:1450: inode 6816
[86809.295631] EXT4-fs (mmcblk0p7): error count since last fsck: 5
[86809.295703] EXT4-fs (mmcblk0p7): initial error at time 4: ext4_journal_check_start:56
[86809.295741] EXT4-fs (mmcblk0p7): last error at time 1507828026: ext4_find_entry:1450: inode 6816
[89235.510964] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[89235.677149] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[89235.677179] mmcblk0: error -110 transferring data, sector 6998016, nr 256, cmd response 0x900, card status 0xb00
[89235.678237] mmcblk0: retrying using single block read
[173318.501166] EXT4-fs (mmcblk0p7): error count since last fsck: 5
[173318.501237] EXT4-fs (mmcblk0p7): initial error at time 4: ext4_journal_check_start:56
[173318.501275] EXT4-fs (mmcblk0p7): last error at time 1507828026: ext4_find_entry:1450: inode 6816Again, nothing out of the ordinary. The EXT4-fs comments, 300s after boot and then daily afterwards, are well known. One error while idling for two days. That's near okay.
Then, I did some tinkering (copying files, repeatedly loading/exiting ipython):
Code:
[192228.340598] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192228.506799] mmcblk0: error -110 transferring data, sector 2108560, nr 512, cmd response 0x900, card status 0x0
[192228.507897] mmcblk0: retrying using single block read
[192228.596614] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192228.762782] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192228.762812] mmcblk0: error -110 transferring data, sector 2110096, nr 512, cmd response 0x900, card status 0xb00
[192228.763946] mmcblk0: retrying using single block read
[192228.856611] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192229.022789] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192229.022818] mmcblk0: error -110 transferring data, sector 2112656, nr 512, cmd response 0x900, card status 0xb00
[192229.023939] mmcblk0: retrying using single block read
[192229.148618] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192229.314785] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192229.314816] mmcblk0: error -110 transferring data, sector 2264064, nr 512, cmd response 0x900, card status 0xb00
[192229.315958] mmcblk0: retrying using single block read
[192229.424619] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192229.590822] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192229.590852] mmcblk0: error -110 transferring data, sector 2270208, nr 512, cmd response 0x900, card status 0xb00
[192229.591988] mmcblk0: retrying using single block read
[192229.679625] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192229.845811] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192229.845840] mmcblk0: error -110 transferring data, sector 2271232, nr 512, cmd response 0x900, card status 0xb00
[192229.846975] mmcblk0: retrying using single block read
[192229.936631] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192230.102809] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192230.102838] mmcblk0: error -110 transferring data, sector 2273280, nr 512, cmd response 0x900, card status 0xb00
[192230.103979] mmcblk0: retrying using single block read
[192230.192634] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192230.358806] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192230.358835] mmcblk0: error -110 transferring data, sector 2274816, nr 512, cmd response 0x900, card status 0xb00
[192230.359968] mmcblk0: retrying using single block read
[192230.583658] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192230.749834] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192230.749864] mmcblk0: error -110 transferring data, sector 2176512, nr 512, cmd response 0x900, card status 0xb00
[192230.750994] mmcblk0: retrying using single block read
[192230.868652] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192231.034829] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192231.034860] mmcblk0: error -110 transferring data, sector 2184704, nr 512, cmd response 0x900, card status 0xb00
[192231.035993] mmcblk0: retrying using single block read
[192231.108742] mmcblk0: retrying because a re-tune was needed
[192231.310628] dwmmc_rockchip ff520000.rksdmmc: Successfully tuned phase to 135
[192231.483668] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192231.649842] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192231.649873] mmcblk0: error -110 transferring data, sector 2352128, nr 512, cmd response 0x900, card status 0xb00
[192231.651007] mmcblk0: retrying using single block read
[192231.738666] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[192231.904848] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[192231.904878] mmcblk0: error -110 transferring data, sector 2353152, nr 512, cmd response 0x900, card status 0xb00...And there we are again. The r/w speed while copying files is okay-ish, I guess: Using rsync (I have no idea whether this is appropriate for benchmarking) I get +50MB/s. As source and target device are both mmcblk0, I do not expect any world record values. But, being used to class4 SD cards, I am quite happy.
The only thing that bothers me, is my fear of the eMMC dying or corrupting. It would make me more than happy, if someone could be as kind as to explain to me what's going on with those errors.
Thanks, -ac
