Up Squared on Linux - getting mmc error messages
Andy Carlson
New Member Posts: 6 ✭
I have an 8GB, 128GB N4200 Up Squared. I installed Fedora, with the 4.11 kernel. I have been getting a lot of timeout errors on the mmc. Here is an example:
[Sun Jun 11 21:26:31 2017] mmc0: Timeout waiting for hardware interrupt.
[Sun Jun 11 21:26:31 2017] sdhci: =========== REGISTER DUMP (mmc0)===========
[Sun Jun 11 21:26:31 2017] sdhci: Sys addr: 0x00000008 | Version: 0x00001002
[Sun Jun 11 21:26:31 2017] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[Sun Jun 11 21:26:31 2017] sdhci: Argument: 0x028a9988 | Trn mode: 0x0000003b
[Sun Jun 11 21:26:31 2017] sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[Sun Jun 11 21:26:31 2017] sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[Sun Jun 11 21:26:31 2017] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[Sun Jun 11 21:26:31 2017] sdhci: Timeout: 0x00000004 | Int stat: 0x00000000
[Sun Jun 11 21:26:31 2017] sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[Sun Jun 11 21:26:31 2017] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[Sun Jun 11 21:26:31 2017] sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[Sun Jun 11 21:26:31 2017] sdhci: Cmd: 0x0000123a | Max curr: 0x00000000
[Sun Jun 11 21:26:31 2017] sdhci: Host ctl2: 0x0000008d
[Sun Jun 11 21:26:31 2017] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000027034e200
[Sun Jun 11 21:26:31 2017] sdhci: ===========================================
[Sun Jun 11 21:26:31 2017] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[Sun Jun 11 21:26:31 2017] mmcblk0: error -110 transferring data, sector 42637704, nr 8, cmd response 0x0, card status 0x0
Any ideas what is going on? Things hang for a few seconds when this happens. Thanks.
[Sun Jun 11 21:26:31 2017] mmc0: Timeout waiting for hardware interrupt.
[Sun Jun 11 21:26:31 2017] sdhci: =========== REGISTER DUMP (mmc0)===========
[Sun Jun 11 21:26:31 2017] sdhci: Sys addr: 0x00000008 | Version: 0x00001002
[Sun Jun 11 21:26:31 2017] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[Sun Jun 11 21:26:31 2017] sdhci: Argument: 0x028a9988 | Trn mode: 0x0000003b
[Sun Jun 11 21:26:31 2017] sdhci: Present: 0x1fff0001 | Host ctl: 0x0000003d
[Sun Jun 11 21:26:31 2017] sdhci: Power: 0x0000000b | Blk gap: 0x00000080
[Sun Jun 11 21:26:31 2017] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[Sun Jun 11 21:26:31 2017] sdhci: Timeout: 0x00000004 | Int stat: 0x00000000
[Sun Jun 11 21:26:31 2017] sdhci: Int enab: 0x02ff000b | Sig enab: 0x02ff000b
[Sun Jun 11 21:26:31 2017] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[Sun Jun 11 21:26:31 2017] sdhci: Caps: 0x546ec881 | Caps_1: 0x80000807
[Sun Jun 11 21:26:31 2017] sdhci: Cmd: 0x0000123a | Max curr: 0x00000000
[Sun Jun 11 21:26:31 2017] sdhci: Host ctl2: 0x0000008d
[Sun Jun 11 21:26:31 2017] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x000000027034e200
[Sun Jun 11 21:26:31 2017] sdhci: ===========================================
[Sun Jun 11 21:26:31 2017] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[Sun Jun 11 21:26:31 2017] mmcblk0: error -110 transferring data, sector 42637704, nr 8, cmd response 0x0, card status 0x0
Any ideas what is going on? Things hang for a few seconds when this happens. Thanks.
Comments
-
https://up-community.org/forum/general-discussion-up2/1898-up2-storage-getting-readonly-frequently
I think the issue is same as above. -
I tried Ubuntu 17.04, with the same outcome. Guess I will wait for Ubilinux 4.
-
Is the plan to push the Up Squared kernel patches upstream so they will be included in the mainline kernel?
-
We are investigating the issue and we will come back to you before the end of the week with an update.
Thanks for reporting the issue.
Note: naclosagc, for any question that is out off topic, please feel free to open a new one, so we could better manage the information and clarify each specific question on his own thread. thanks!