iMX6 SabreSD Kernel panic

cancel
Showing results for 
Search instead for 
Did you mean: 

iMX6 SabreSD Kernel panic

559 Views
sajjadahmed
Contributor II

I'm using an iMX6 sabreSD board, SCH-27516 Rev B5, 700-27516 Rev X5

  • sabreSD board boots fine with NXP i.MX Release Distro 4.14-sumo (sumo)
  • The issue is when loaded with Kernel v4.19 (warrior release) and the latest release, NXP i.MX Release Distro 5.4-zeus (zeus)! L5.4.3_1.0.0_MX6QDLSOLOX, the kernel goes to panic, see below logs.

Supposedly, this is a memory issue only appears on older sabreSD boards, kindly point to some solution to run the latest kernel on older board revisions, also mention board revisions which are currently supported by NXP to run the latest sources.

[   10.659647] 8<--- cut here ---
[   10.666423] Unable to handle kernel NULL pointer dereference at virtual address 00000001
[   10.682163] pgd = (ptrval)
[   10.690018] [00000001] *pgd=38ea9831, *pte=00000000, *ppte=00000000
[  OK  ] Started Network Time S[   10.711515] Internal error: Oops: 17 [#1] PREEMPT SMP ARM
 nchronization.[
   10.717929] Modules linked in: galcore(O)
[   10.723793] CPU: 1 PID: 305 Comm: udevadm Tainted: G           O      5.4.3-lts-lf-5.4.y+gf8118585ee3c #1
[   10.733388] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
[   10.740000] PC is at lookup_fast+0x17c/0x2bc
[   10.744300] LR is at kernfs_dop_revalidate+0xb4/0xc4
[   10.749269] pc : [<802386b0>]    lr : [<802a7284>]    psr: 20010013
[   10.755539] sp : a8f1fd98  ip : a8910000  fp : d0d0d0d0
[   10.760796] r10: a8f1fdd0  r9 : a80379d0  r8 : a62deaa0
[   10.760805] r7 : a8f1fdcc  r6 : d0d0d0d0  r5 : 00000001  r4 : a80379d0
[   10.760813] r3 : a8910000  r2 : 00000000  r1 : 00000000  r0 : 00000001
[   10.760826] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[   10.760836] Control: 10c5787d  Table: 3905004a  DAC: 00000051
[   10.760854] Process udevadm (pid: 305, stack limit = 0x(ptrval))
[  OK  ] Created slice system-systemd\x2dbacklight.slice.

Error log attached,

-Sajjad Ahmed

Labels (2)
0 Kudos
4 Replies

121 Views
leonardoprates
Contributor I

Did you find a solution? I have got the same issue at same releases.

0 Kudos

73 Views
leonardoprates
Contributor I

In my case the main reason is systemd, I just changed to sysvinit.

0 Kudos

405 Views
gusarambula
NXP TechSupport
NXP TechSupport

Helo Sajjad Ahmed,

I couldn’t find reports on the latest BSPs not working on that specific version of the SABRE board. I will open an internal escalation to see if the settings and patches on the latest BSPs only support certain revisions of the board and what information we have on which changes would be required. I will let you know as soon as I have more information.


Regards,

0 Kudos

405 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Sajjad Ahmed,

I received have two suggestions from our experts. Firstly, they have found two patches that differ on the two releases which may help. Would you please apply them and do some testing to see if it helps?

 

    9afc6429e1e6 MLK-23997 arm: dts: imx6qdl: increase the PAD drive strength for usdhc2

    https://source.codeaurora.org/external/imx/linux-imx/commit/?h=imx_5.4.24_2.1.0&id=9afc6429e1e60c415...

 

     42f457848d07 ARM: dts: imx6qdl-sabresd: Remove incorrect power supply assignment

     https://source.codeaurora.org/external/imx/linux-imx/commit/?h=imx_5.4.24_2.1.0&id=42f457848d07be158...

 

The second suggestion is using the zImage type of Kenrel. From the log it seems that you may be using an uImage type of kernel and loading it to address 0x20000000. If you could try loading the zImage kernel in the default address that U-Boot provides, that’s also worth looking at. (Albeit it wouldn’t explain why the same exact variables work on the newer boards).

I hope this helps!

Regards,

0 Kudos