AnsweredAssumed Answered

kernel panic in xhci_bus_resume?

Question asked by Takashi Matsuzawa on Feb 12, 2017
Latest reply on Feb 13, 2017 by igorpadykov

We are testing fido based system (based on freescale imx-3.14.52-1.1.0_ga) on SABRE-AI, and occasionally experiencing a kernel panic, seemingly happening in USB host driver.
The log always look like below, where I see function name xhci_bus_resume.
(The whole log is also attached.)


I have googledd for the clue, but I could not find (so far) similar bug reports.
But I have learned that this function has something to do with CONFIG_PM kernel setting.
The issue also reproduced when there is no USB device attached to the port.

Any experience or suggestion to avoid this issue?


Switching to the newer versions of BSP is one idea, but I want to do so afater identifying the cause of this issue: What it is and what changes in the kernel will be fixing it.


Exception stack(0xd827bbd0 to 0xd827bc18)
bbc0: 00000000 60000193 00000000 00000000
bbe0: 00000018 80b4c588 80ae3634 00000007 00000001 60000113 00000000 00000000
bc00: 0000000f d827bc18 80776dcc 8006bb38 60000113 ffffffff
[<80012240>] (__irq_svc) from [<8006bb38>] (vprintk_emit+0x198/0x4fc)
[<8006bb38>] (vprintk_emit) from [<8076f4ec>] (printk+0x34/0x44)
[<8076f4ec>] (printk) from [<8001a304>] (show_pte+0x4c/0x10c)
[<8001a304>] (show_pte) from [<8076f22c>] (__do_kernel_fault.part.11+0x50/0x74)
[<8076f22c>] (__do_kernel_fault.part.11) from [<8001a628>] (do_page_fault+0x264/0x3e4)
[<8001a628>] (do_page_fault) from [<800083bc>] (do_DataAbort+0x38/0x98)
[<800083bc>] (do_DataAbort) from [<800121d8>] (__dabt_svc+0x38/0x60)
Exception stack(0xd827bde8 to 0xd827be30)
bde0: ee7260b0 00000001 00000000 00000000 00000000 d827bf00
be00: ee7260b0 ee726068 ee71e030 80ad6804 80ad65d0 ee72602c 00001fb3 d827be30
be20: 804f7df0 80466674 00000013 ffffffff
[<800121d8>] (__dabt_svc) from [<80466674>] (xhci_bus_resume+0xfc/0x33c)
[<80466674>] (xhci_bus_resume) from [<80ba215c>] (cpufreq_transition_notifier_list+0x18/0x80)
Code: 00000000 00200200 80b4a7ac 80b4a7ac (80b4a7b4)
---[ end trace a948f2b7fc7bc740 ]---

Original Attachment has been moved to: