mmc: Timeout waiting for hardware interrupt

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

mmc: Timeout waiting for hardware interrupt

1,476 Views
kecan
Contributor I

linux kernel 3.14.28,and board is imx6q.

issue:

mmc3: Timeout waiting for hardware interrupt.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 0 at drivers/mmc/host/sdhci.c:997 sdhci_send_command+0x888/0xdf8()
Modules linked in: [last unloaded: wdog_control]
CPU: 1 PID: 0 Comm: swapper/1 Tainted: G O 3.14.28-1.0.0_ga+g91cf351 #3
[<80015638>] (unwind_backtrace) from [<80011714>] (show_stack+0x10/0x14)
[<80011714>] (show_stack) from [<8071407c>] (dump_stack+0x7c/0xbc)
[<8071407c>] (dump_stack) from [<8002d798>] (warn_slowpath_common+0x70/0x8c)
[<8002d798>] (warn_slowpath_common) from [<8002d850>] (warn_slowpath_null+0x1c/0x24)
[<8002d850>] (warn_slowpath_null) from [<804d74e4>] (sdhci_send_command+0x888/0xdf8)
[<804d74e4>] (sdhci_send_command) from [<804d7e5c>] (sdhci_timeout_timer+0x74/0xb8)
[<804d7e5c>] (sdhci_timeout_timer) from [<8003778c>] (call_timer_fn.isra.33+0x24/0x88)
[<8003778c>] (call_timer_fn.isra.33) from [<80037954>] (run_timer_softirq+0x164/0x1e4)
[<80037954>] (run_timer_softirq) from [<800317cc>] (__do_softirq+0x140/0x248)
[<800317cc>] (__do_softirq) from [<80031b5c>] (irq_exit+0xb8/0xf4)
[<80031b5c>] (irq_exit) from [<8000ed90>] (handle_IRQ+0x44/0x90)
[<8000ed90>] (handle_IRQ) from [<8000856c>] (gic_handle_irq+0x2c/0x5c)
[<8000856c>] (gic_handle_irq) from [<80012200>] (__irq_svc+0x40/0x70)
Exception stack(0xa80a7f50 to 0xa80a7f98)
7f40: a80a7f98 3b9aca00 17c21b38 00020933
7f60: 80e94548 80e94548 ab72c0d0 00000000 178591d2 00020933 a80a6000 00000000
7f80: 00000017 a80a7f98 00000009 804c2364 000c0013 ffffffff
[<80012200>] (__irq_svc) from [<804c2364>] (cpuidle_enter_state+0x54/0xe4)
[<804c2364>] (cpuidle_enter_state) from [<804c24a8>] (cpuidle_idle_call+0xb4/0x14c)
[<804c24a8>] (cpuidle_idle_call) from [<8000f0bc>] (arch_cpu_idle+0x8/0x44)
[<8000f0bc>] (arch_cpu_idle) from [<80067a3c>] (cpu_startup_entry+0x100/0x14c)
[<80067a3c>] (cpu_startup_entry) from [<10008624>] (0x10008624)
---[ end trace ae8abc666c59473e ]---

then restart.

Labels (1)
0 Kudos
3 Replies

933 Views
igorpadykov
NXP Employee
NXP Employee

Hi zhenyang

restarting and "exception" messages may point to memory problems,

so may be suggested first to check memory and update image with new memory

calibration settings

https://community.nxp.com/docs/DOC-105652 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

933 Views
kecan
Contributor I

We have checked it with the checking tool, but this problem still occurs in operation. Is there any other reason for this? The version of our verification tool is 2.6. Will this affect us?

0 Kudos

933 Views
igorpadykov
NXP Employee
NXP Employee

could you try linux from nxp repository

linux-imx - i.MX Linux kernel 

0 Kudos