Mmc0 timeout in imx6q observed

Technical Support
, ,
1

I’ve seen an isolated anomaly like this, just once; wondering what it means?

[ 5360.472574] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=19
[ 5360.480161] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 5360.486608] mmc0: sdhci: Sys addr:  0x100af000 | Version:  0x00000002
[ 5360.493053] mmc0: sdhci: Blk size:  0x00000200 | Blk cnt:  0x00000000
[ 5360.499500] mmc0: sdhci: Argument:  0x0035d758 | Trn mode: 0x0000002b
[ 5360.505945] mmc0: sdhci: Present:   0x01fd8008 | Host ctl: 0x00000031
[ 5360.512389] mmc0: sdhci: Power:     0x00000002 | Blk gap:  0x00000080
[ 5360.518833] mmc0: sdhci: Wake-up:   0x00000008 | Clock:    0x0000001f
[ 5360.525277] mmc0: sdhci: Timeout:   0x0000008f | Int stat: 0x00000003
[ 5360.531721] mmc0: sdhci: Int enab:  0x107f100b | Sig enab: 0x107f100b
[ 5360.538165] mmc0: sdhci: AC12 err:  0x00000000 | Slot int: 0x00000003
[ 5360.544611] mmc0: sdhci: Caps:      0x07eb0000 | Caps_1:   0x0000a007
[ 5360.551056] mmc0: sdhci: Cmd:       0x0000193a | Max curr: 0x00ffffff
[ 5360.557500] mmc0: sdhci: Resp[0]:   0x00000900 | Resp[1]:  0xffffffff
[ 5360.563944] mmc0: sdhci: Resp[2]:   0x320f5913 | Resp[3]:  0x00000900
[ 5360.570387] mmc0: sdhci: Host ctl2: 0x00000000
[ 5360.574834] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x7c078228
[ 5360.581276] mmc0: sdhci: ============================================
[ 5370.712583] mmc0: Timeout waiting for hardware interrupt. retries left=0 opcode=c
[ 5370.720084] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 5370.726531] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x00000002
[ 5370.732976] mmc0: sdhci: Blk size:  0x00000200 | Blk cnt:  0x00000000
[ 5370.739423] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000023
[ 5370.745867] mmc0: sdhci: Present:   0x01fd8009 | Host ctl: 0x00000031
[ 5370.752311] mmc0: sdhci: Power:     0x00000002 | Blk gap:  0x00000080
[ 5370.758756] mmc0: sdhci: Wake-up:   0x00000008 | Clock:    0x0000001f
[ 5370.765201] mmc0: sdhci: Timeout:   0x0000008f | Int stat: 0x00010000
[ 5370.771645] mmc0: sdhci: Int enab:  0x107f100b | Sig enab: 0x107f100b
[ 5370.778090] mmc0: sdhci: AC12 err:  0x00000000 | Slot int: 0x00000003
[ 5370.784534] mmc0: sdhci: Caps:      0x07eb0000 | Caps_1:   0x0000a007
[ 5370.790978] mmc0: sdhci: Cmd:       0x00000cdb | Max curr: 0x00ffffff
[ 5370.797422] mmc0: sdhci: Resp[0]:   0x00000900 | Resp[1]:  0xffffffff
[ 5370.803865] mmc0: sdhci: Resp[2]:   0x320f5913 | Resp[3]:  0x00000900
[ 5370.810308] mmc0: sdhci: Host ctl2: 0x00000000
[ 5370.814755] mmc0: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[ 5370.821197] mmc0: sdhci: ============================================
[ 5371.132564] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 5371.138091] 	0-...: (1 GPs behind) idle=6e3/140000000000000/0 softirq=180225/180227 fqs=1051 
[ 5371.146618] 	(detected by 3, t=2103 jiffies, g=69274, c=69273, q=2443)
2

Hi @dgribben

Thanks for the feedback.

This issue could be related to a mmc driver and gpu bugs in the old kernels. Did you see this issue also on Bsp 3.0.4?

Best regards,
Jaski

3

I’ve never seen this issue before this past Monday. It only happened one time on one system. Will advise if I ever see it again.

Thanks,
–Doug

4

Ok, Thanks for your Input.