i.MX8QXP boot linux, Kernel panic

415835023 — Wed, 13 May 2020 03:08:40 GMT

我使用的是imx8qxp板子，3G内存，32GEMMC；烧录linux板子系统以后，内核启动崩溃，请帮忙分析下问题原因

由于上传内容限制、只能贴出一部分的log、详细请参照附件、谢谢。

imx8qxpmek login: [ 15.433370] random: crng init done
[ 15.436793] random: 7 urandom warning(s) missed due to ratelimiting
[ 15.487968] device l2tpapn0 entered promiscuous mode
[ 46.438585] Unable to handle kernel paging request at virtual address 4d560085
[ 46.445849] Mem abort info:
[ 46.448706] Exception class = DABT (current EL), IL = 32 bits
[ 46.454656] SET = 0, FnV = 0
[ 46.457736] EA = 0, S1PTW = 0
[ 46.460892] Data abort info:
[ 46.463778] ISV = 0, ISS = 0x00000021
[ 46.467637] CM = 0, WnR = 0
[ 46.470632] user pgtable: 4k pages, 48-bit VAs, pgd = ffff8000066f1000
[ 46.477212] [000000004d560085] *pgd=0000000000000000
[ 46.482229] Internal error: Oops: 96000021 [#1] PREEMPT SMP
[ 46.487808] Modules linked in:
[ 46.490870] CPU: 3 PID: 1160 Comm: systemd-journal Not tainted 4.14.78 #1
[ 46.497660] Hardware name: Freescale i.MX8QXP MEK (DT)
[ 46.502803] task: ffff800014579800 task.stack: ffff00000d3c0000
[ 46.508738] PC is at unix_stream_read_generic+0x3f4/0x738
[ 46.514143] LR is at unix_stream_read_generic+0x2c8/0x738
[ 46.519544] pc : [<ffff0000086f1764>] lr : [<ffff0000086f1638>] pstate: 40000145
[ 46.526944] sp : ffff00000d3c3c00
[ 46.530252] x29: ffff00000d3c3c00 x28: 0000000000000000
[ 46.535569] x27: ffff800001f58000 x26: ffff800014d62948
[ 46.540886] x25: 0000000000000000 x24: 0000000000000000
[ 46.546203] x23: ffff800001f58028 x22: ffff800014d62bc0
[ 46.551519] x21: ffff800014d62880 x20: ffff00000d3c3d10
[ 46.556852] x19: 00000000000007bb x18: 0000ffffeca943ef
[ 46.559550] Unable to handle kernel paging request at virtual address 61706172747849
[ 46.559553] Mem abort info:
[ 46.559556] Exception class = DABT (current EL), IL = 32 bits
[ 46.559559] SET = 0, FnV = 0
[ 46.559561] EA = 0, S1PTW = 0
[ 46.559562] Data abort info:
[ 46.559564] ISV = 0, ISS = 0x00000004
[ 46.559566] CM = 0, WnR = 0
[ 46.559569] [0061706172747849] address between user and kernel address ranges
[ 46.601618] x17: 0000ffff9a7bc6a0 x16: ffff0000081a13b0
[ 46.606939] x15: 00004fbb9f000000 x14: 00157d3880000000
[ 46.612254] x13: 000000005eba4617 x12: 0000000000000018
[ 46.617570] x11: 0000000015244a63 x10: 000000000000002e
[ 46.622887] x9 : 003b9aca00000000 x8 : 000000000000003f
[ 46.628206] x7 : 0000000000000000 x6 : 0000000000000000
[ 46.633521] x5 : ffff00000882e618 x4 : 0000000000000000
[ 46.638837] x3 : 0000000000000000 x2 : 0000000000000000
[ 46.644154] x1 : ffff800014579800 x0 : 000000004d560085
[ 46.649477] Process systemd-journal (pid: 1160, stack limit = 0xffff00000d3c0000)
[ 46.656962] Call trace:
[ 46.659414] Exception stack(0xffff00000d3c3ac0 to 0xffff00000d3c3c00)
[ 46.665862] 3ac0: 000000004d560085 ffff800014579800 0000000000000000 0000000000000000
[ 46.673695] 3ae0: 0000000000000000 ffff00000882e618 0000000000000000 0000000000000000
[ 46.681531] 3b00: 000000000000003f 003b9aca00000000 000000000000002e 0000000015244a63
[ 46.689369] 3b20: 0000000000000018 000000005eba4617 00157d3880000000 00004fbb9f000000
[ 46.697204] 3b40: ffff0000081a13b0 0000ffff9a7bc6a0 0000ffffeca943ef 00000000000007bb
[ 46.705042] 3b60: ffff00000d3c3d10 ffff800014d62880 ffff800014d62bc0 ffff800001f58028
[ 46.712876] 3b80: 0000000000000000 0000000000000000 ffff800014d62948 ffff800001f58000
[ 46.720712] 3ba0: 0000000000000000 ffff00000d3c3c00 ffff0000086f1638 ffff00000d3c3c00
[ 46.728548] 3bc0: ffff0000086f1764 0000000040000145 ffff00000d3c3c80 ffff0000085e45a8
[ 46.736384] 3be0: 0000ffffffffffff 000000000000001c ffff00000d3c3c00 ffff0000086f1764
[ 46.744227] [<ffff0000086f1764>] unix_stream_read_generic+0x3f4/0x738
[ 46.750669] [<ffff0000086f1b48>] unix_stream_recvmsg+0x30/0x38
[ 46.756509] [<ffff0000085e2b04>] sock_read_iter+0x7c/0xc0
[ 46.761913] [<ffff0000081a0cac>] __vfs_read+0xac/0x108
[ 46.767053] [<ffff0000081a0d94>] vfs_read+0x8c/0x130
[ 46.772023] [<ffff0000081a13f8>] SyS_read+0x48/0xb0
[ 46.776903] Exception stack(0xffff00000d3c3ec0 to 0xffff00000d3c4000)

Re: i.MX8QXP boot linux, Kernel panic

igorpadykov — Wed, 13 May 2020 11:04:06 GMT

Hi Edwin

for custom board it is necessary to run ddr test and use

MX 8/8X DDR Register Programming Aid (RPA) tool,

integrate it to SCFW: SCFW Porting Kit

i.MX 8/8X Family DDR Tools Release

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

Re: i.MX8QXP boot linux, Kernel panic

415835023 — Fri, 22 May 2020 09:53:24 GMT

Hi igorpadykov

we have tested the board using MX8_DDR_Tester and memtester tool, but we have not found any problems.
We have asked questions in the Linux Kernel community too.
They think it should be a driver problem.
Therefore, please help us to resolve the problem.
The reproduction rate of this issue is not high, but it can be reproduced.
so if you want to add log and reproduce the issue, please contact us.

Re: i.MX8QXP boot linux, Kernel panic

igorpadykov — Fri, 22 May 2020 14:42:31 GMT

please try latest C0 revision i.MX 8X C0 Migration Guide Migrating from i.MX 8X B0 to i.MX 8X C0

with L5.4.3 : Linux 5.4.3_1.0.0 Documentation

Best regards
igor

Re: i.MX8QXP boot linux, Kernel panic

415835023 — Sat, 23 May 2020 05:17:07 GMT

I consulted our engineer. Our board is B0, so the C0 revision your provide to us can not be used on this board.

In addition, is there any changes related to this issue in C0 revision?

Can these related changes be patched into B0 revision and provided to us?

topic i.MX8QXP boot linux, Kernel panic in i.MX Processors

i.MX8QXP boot linux, Kernel panic

Re: i.MX8QXP boot linux, Kernel panic

Re: i.MX8QXP boot linux, Kernel panic

Re: i.MX8QXP boot linux, Kernel panic

Re: i.MX8QXP boot linux, Kernel panic