Mmc0 timeout waiting err on tx2

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
,
1

Hi, all. our device is based on tx2 with custom carrier board. Most of time it’s works fine, but today I found that it often has the following errors.

[ 6.369730] Waiting for root device /dev/mmcblk0p1…
[ 12.971902] mmc0: Timeout waiting for hardware interrupt.
[ 12.978528] sdhci: =========== REGISTER DUMP (mmc0)===========
[ 12.985536] sdhci: Sys addr: 0x00000000 | Version: 0x00000404
[ 12.992546] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000001
[ 12.999551] sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
[ 13.006543] sdhci: Present: 0x01fb02f6 | Host ctl: 0x00000034
[ 13.013551] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 13.020547] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 13.027506] sdhci: Timeout: 0x0000000e | Int stat: 0x00000000
[ 13.034428] sdhci: Int enab: 0x02ff000b | Sig enab: 0x02fc000b
[ 13.041346] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 13.048253] sdhci: Caps: 0x3f6cd08c | Caps_1: 0x18006f73
[ 13.055179] sdhci: Cmd: 0x0000083a | Max curr: 0x00000000
[ 13.062110] sdhci: Host ctl2: 0x0000300d
[ 13.067150] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x0000000080000010
[ 13.074815] sdhci: ===========================================
[ 13.081858] mmc0: post init failed for hs400 mode
[ 13.087754] mmc0: error -110 whilst initialising MMC card

timeout waiting err.log (146.4 KB)

Restart the device, this error may not occur. please give me some advice to fix it, thanks.

3

It is also rel-28 ? Which rel-28? Is it able to reproduce with devkit?

4

hi, WayneWWW
yes ,it’s rel-28.3.1. I have not tested it on devkit because this error only occurs randomly and is not mandatory. I’ll try testing it on devkit today.

5

Please check if rel-28.5 still has this issue or not. If there is not, then we need to see which patch is missing between rel-28.5 and rel-28.3.1.

6

this device is completely using rel-28.3.1, it isn’t using part of rel-28.5. Not a problem caused by combination use.

7

不是… 我的意思是指我需要知道rel-28.5已經修掉這個問題了沒有… 所以才需要你移到rel-28.5測試 甚至是rel-32上面測試
No, I mean I need to know rel-28.5 has fixed this issue or not. That is why asking you to move to rel-28.5 or even rel-32 to test.

8

Ok, I’ll give it a try.