iMX8QM end Kernel panic

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

iMX8QM end Kernel panic

3,615 Views
Ray_chentao
Contributor I

 

hello,

I am having a kernel panic problem with the processor  iMX8QM. The DDR Stress Test is OK, what can I do to debug this problem, the error log is attached.

CPU: Freescale i.MX8QM revB A53 at 1200 MHz at 55C
Model: Freescale i.MX8QM MEK
Board: iMX8QM MEK
Boot: MMC0
DRAM: 6 GiB

 

[ 2.538851] [<ffff000008083230>] el1_irq+0xb0/0x124
[ 2.546978] imx8-dpr-channel 570f0000.dpr-channel: Linked as a consumer to 57060000.prg
[ 2.554505] [<ffff000008085820>] arch_cpu_idle+0x10/0x18
[ 2.554508] [<ffff00000810d8a0>] do_idle+0x120/0x1e0
[ 2.554511] [<ffff00000810dafc>] cpu_startup_entry+0x24/0x28
[ 2.554518] [<ffff00000808fac8>] secondary_start_kernel+0x110/0x120
[ 2.564677] imx8-dpr-channel 57100000.dpr-channel: Linked as a consumer to 57070000.prg
[ 2.570352] Code: bad PC value
[ 2.570365] ---[ end trace bcd121847d8b8700 ]---
[ 2.578229] imx8-dpr-channel 57100000.dpr-channel: Linked as a consumer to 57080000.prg
[ 2.586022] Kernel panic - not syncing: Fatal exception in interrupt
[ 2.586026] SMP: stopping secondary CPUs
[ 2.593865] Kernel Offset: disabled
[ 2.593868] CPU features: 0x180200d
[ 2.593869] Memory Limit: none
[ 2.882678] ---[ end Kernel panic - not syncing: Fatal exception in interrupt

0 Kudos
Reply
3 Replies

2,402 Views
achintala
Contributor I

How was this issue solved? @Ray_chentao - I'm running into same problem, would be great to learn from your experience on solving this.

0 Kudos
Reply

3,603 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hi @Ray_chentao 

You should check your DDR Calibration again.

0 Kudos
Reply

3,588 Views
Ray_chentao
Contributor I

Hi, @Qmiller, thanks a lot.

How could I check my DDR Calibration?  Use i.MX8 DDR Tools and run the DDR stress test?

The DDR stress test is succeed at DDR clock 800MHz and 1200MHz, but  fail at 1600MHz.

We're trying to config my iMX8QM work at DDR clock 800MHz, but the problem was still occurred with the same log.

 

 

0 Kudos
Reply