Bliss OS (Pinebook) 20170919 [Oct 13] | Bliss OS (PINE A64(+)) 20170919 [Oct 13] | Linux Images (ROCK64) 0.5.10-118 [Oct 2] | Android Images (ROCK64) 0.3.4-86 [Oct 2] | Android 6.0.1 (PINE A64-LTS / SOPINE) 20170726 [Sep 29] | Android 7.1 (Pinebook) 0.3.10-66 [Sep 19] | Android 7.1 (PINE A64(+)) 0.3.10-66 [Sep 19] | Android 7.1 (SOPINE) 0.3.10-66 [Sep 19] | PINE64 Installer v2.0.0-beta.3 [Sep 12]

Getting Started | Visit the WIKI | IRC Logs | Forum Rules/Policy


Receiving errors about eMMC (?)
#1
TL;DR:  Ayufans latest eMMC-Mate-image. Strange errors in dmesg. See snippet below. Need help interpreting.

----------------

Hi! After some weeks of using my rock64 as bookshelf decoration, I'm finally starting to tinker with it.

At first, I hit some smaller bumps like using the official Mate image and loosing USB power after login.

Now I'm using ayufans latest eMMC Mate image. Installation to the eMMC module was super unproblematic. First reboot worked fine. Did some basic first login stuff (keyboard-layout, password, ...), and issued a reboot command. System tried to start, but delivered a black screen with a blinking cursor. I let it sit like this for about fifteen minutes ("just let it work. who knows, what's going on inside"), then I did a hard reset. System started to graphical login prompt. Typed in password, login box vanished, and that was it. Again fifteen minutes, this time only with the blue rock64 background. 
I grew a bit concerned, but after another hard reset, the system bootet up and everything was fine. And since this last reset it's been stable and useful: No more freezes, quick boot and login, USB power and ethernet woking fine, all looking bright and shiny. 
 
Then I made the error and issued the dmesg command. You know, just out of curiosity. Not that I could understand what it tells me. Just wanted to see what's going on. 
And there I saw them: Errors. Colored brightly red, lots of errors about mmcblk0.
 
Small snippet of dmesg output:

Code:
[   23.781898] mmcblk0: retrying using single block read
[   23.825835] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   23.991919] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[   23.991933] mmcblk0: error -110 transferring data, sector 3279888, nr 256, cmd response 0x900, card status 0xb00
[   23.992879] mmcblk0: retrying using single block read
[   24.120340] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
[   24.120355] mmcblk0: retrying because a re-tune was needed
[   24.321852] dwmmc_rockchip ff520000.rksdmmc: Successfully tuned phase to 135
[   24.340830] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   24.506898] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[   24.506914] mmcblk0: error -110 transferring data, sector 265240, nr 232, cmd response 0x900, card status 0xb00
[   24.507855] mmcblk0: retrying using single block read
[   24.577818] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   24.742932] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[   24.742947] mmcblk0: error -110 transferring data, sector 10191680, nr 144, cmd response 0x900, card status 0xb00
[   24.743909] mmcblk0: retrying using single block read
[   24.835882] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   24.850620] tty_port_close_start: tty->count = 1 port count = 2.
[   25.001946] mmcblk0: error -110 transferring data, sector 5610720, nr 32, cmd response 0x900, card status 0x0
[   25.002839] mmcblk0: retrying using single block read
[   25.306353] mmcblk0: retrying because a re-tune was needed
[   25.599857] dwmmc_rockchip ff520000.rksdmmc: Successfully tuned phase to 135
[   35.494818] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   35.660947] mmcblk0: error -110 transferring data, sector 8489664, nr 152, cmd response 0x900, card status 0x0
[   35.661864] mmcblk0: retrying using single block read
[   35.707819] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   35.873936] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[   35.873950] mmcblk0: error -110 transferring data, sector 8486664, nr 224, cmd response 0x900, card status 0xb00
[   35.874895] mmcblk0: retrying using single block read
[   38.238823] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   38.404938] mmcblk0: error -110 transferring data, sector 3006264, nr 256, cmd response 0x900, card status 0x0
[   38.405854] mmcblk0: retrying using single block read
[   38.830921] mmcblk0: retrying because a re-tune was needed
[   39.124857] dwmmc_rockchip ff520000.rksdmmc: Successfully tuned phase to 135
[   39.864829] dwmmc_rockchip ff520000.rksdmmc: Unexpected command timeout, state 3
[   40.030909] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00
[   40.030923] mmcblk0: error -110 transferring data, sector 5127832, nr 56, cmd response 0x900, card status 0xb00
[   40.031846] mmcblk0: retrying using single block read

Seeing similar errors after reboot(s) made me really concerned. I tried my google-fu, but with limited success: 
  • Googling the "dwmmc [...] Unexpected command timeout [...]" line did not bring up any results.
  • Googling the "error -115" line also did not yield useful hints (or I did not recognise them as such)
  • Googling the "error -110" line was to some extent successful:
I stumbled across a NXP forum thread discussing a very similar error message. Their accepted answer was that the SD-card was "too fast". I don't know whether this is correct or not, but also their problem description is missing the "error -115". (And I am using the 32GB eMMC module, not an SD-card.)

Whilest playing around with the rock64 and dmesg, I made some further observations: 
  • When idling, usually no further errors occur. When doing stuff (opening programs, ...), errors continue.
  • The amount of errors is random. I even had one completly error-free boot.
  • In dmesg-output, at ~305 sec runtime, I get three EXT4-fs entries, telling about number of errors since last fsck.
  • Only the "-110" error is colored red, the "-115" is not. (Maybe less dangerous?)
 
To clarify: I have a tiny bit of linux experience, but really tiny. Someone showed me "dmesg", now all I know about errors and logging in Linux is dmesg. I also have a Raspberry Pi, and installed Owncloud on it (by following a tutorial). But that's really where my abilities end. To the most part I have no idea what's going on, it feels like stumbling around in the fog. But I am willing to learn about Linux and Rock64 (even though I really should invest my time in other things right now).

I would be very grateful, if someone could shed some light on these error issues.

-ac

_______
Side note to board administrators: I could not decide whether to put this thead under "Linux" or under "Hardware", so I ended up in "General Discussion" - just to be on the wrong side either way. Feel free to move this thread around. I am very new to forums (at least as active participant) and I am sorry.
Reply
#2
...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: 
  • 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). 
...but nothing of this come unexpectedly.


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 6816


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):

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
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
Brick How to Write an Image to the eMMC Module Tutorial MarkHaysHarris777 43 2,851 10-13-2017, 04:09 AM
Last Post: MarkHaysHarris777
  USB -> eMMC adapter coming soon Luke 5 278 10-12-2017, 02:00 AM
Last Post: erchache2000
  Dual boot microsd/eMMc? chitenavi 2 153 10-06-2017, 02:03 PM
Last Post: chitenavi
  Easiest way to flash eMMC tycoonbob 13 547 09-30-2017, 09:33 PM
Last Post: WhiskerBiscuit
  I've got a emmc to sd adapter to write image fbms 0 207 08-28-2017, 04:29 PM
Last Post: fbms
  Emmc error muzam2 0 147 08-19-2017, 11:02 AM
Last Post: muzam2
  Rock64 performance: eMMC / SD Card / USB3 (SSD/HDD) Blastmun 15 1,243 08-16-2017, 08:44 AM
Last Post: stuartiannaylor
  How to install and boot ROCK64 from eMMC? kershaw 32 3,496 08-15-2017, 07:41 AM
Last Post: MarkHaysHarris777
  eMMC ? stuartiannaylor 2 321 08-07-2017, 10:47 AM
Last Post: Luke

Forum Jump:


Users browsing this thread: 1 Guest(s)