From: Vignesh Raman <vignesh.raman@collabora.com>
To: linux-amlogic <linux-amlogic@lists.infradead.org>
Cc: neil.armstrong@linaro.org, khilman@baylibre.com,
jbrunet@baylibre.com, martin.blumenstingl@googlemail.com,
sboyd@kernel.org, daniels <daniels@collabora.com>,
Daniel Stone <daniel@fooishbar.org>,
lumag@kernel.org, robdclark <robdclark@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: amlogic: Synchronous Abort with v6.15-rc6
Date: Tue, 13 May 2025 15:11:56 +0530 [thread overview]
Message-ID: <eb9281cc-de91-48a4-bbd6-f67ddc67a9dd@collabora.com> (raw)
Hi,
The Amlogic Meson G12B (A311D) SoC board (meson-g12b-a311d-khadas-vim3)
fails to boot with the following logs,
https://gitlab.freedesktop.org/vigneshraman/linux/-/jobs/76210200
02:58:27.819: Starting kernel ...
02:58:27.819: "Synchronous Abort" handler, esr 0x96000010, far 0x51000d8
02:58:27.819: "Synchronous Abort" handler, esr 0x96000010, far 0x51000c8
02:58:27.819: elr: 0000000001002a48 lr : 0000000001002c88 (reloc)
02:58:27.819: elr: 00000000f2f26a48 lr : 00000000f2f26c88
02:58:27.819: x0 : 00000000050fffc0 x1 : 0000000001004383
02:58:27.819: x2 : 00000000f2f6a358 x3 : 000000000000003f
02:58:27.819: x4 : 00000000f4fefffc x5 : 0000000000000010
02:58:27.819: x6 : 00000000f4e5b000 x7 : 00000000050fffa0
02:58:27.819: x8 : 0000000000000008 x9 : 0000000000000001
02:58:27.820: x10: 0000000000000010 x11: 0000000000000004
02:58:27.820: x12: 00000000f4fefc00 x13: 0000000000000000
02:58:27.820: x14: 00000000f4fefc00 x15: 0000000000000000
02:58:27.820: x16: 00000000f2f6d0e0 x17: 0000000000c0c0c0
02:58:27.820: x18: 00000000f0f21d90 x19: 00000000050fffc0
02:58:27.820: x20: 0000000000000000 x21: 000000007ffe9000
02:58:27.820: x22: 0000000000001710 x23: 00000000f0f0e8c0
02:58:27.820: x24: 0000000000000000 x25: 0000000000000000
02:58:27.820: x26: 0000000000000000 x27: 0000000000000000
02:58:27.820: x28: 00000000f0f4f790 x29: 00000000050fff60
02:58:27.820: Code: a9025bf5 f9001bf7 f9400641 36000141 (f9408663)
02:58:27.820: Resetting CPU ...
The board boots successfully in v6.14-rc7, but the issue appears
starting from v6.15-rc1. These tests were run in drm-ci.
On bisecting the kernel, the first bad commit identified by git biscet is,
59c35416f4246aee66b5f5523fdc950b83325d82 is the first bad commit
commit 59c35416f4246aee66b5f5523fdc950b83325d82
Merge: 472863ab2aca e988adcb5dee
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Mar 29 17:23:34 2025 -0700
Merge tag 'clk-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
Please could you look into this issue. Thank you.
Regards,
Vignesh
next reply other threads:[~2025-05-13 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 9:41 Vignesh Raman [this message]
2025-05-13 9:55 ` amlogic: Synchronous Abort with v6.15-rc6 neil.armstrong
2025-05-13 14:26 ` Vignesh Raman
2025-05-13 15:48 ` Jerome Brunet
2025-05-13 15:55 ` Neil Armstrong
2025-05-14 9:36 ` Vignesh Raman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eb9281cc-de91-48a4-bbd6-f67ddc67a9dd@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=daniel@fooishbar.org \
--cc=daniels@collabora.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robdclark@gmail.com \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox