linux-kernel - Re: ARM iMX6sx board fails to boot with kernel 6.17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87ms5lqn1e.fsf@osv.gnss.ru>
Date: Tue, 21 Oct 2025 00:30:05 +0300
From: Sergey Organov <sorganov@...il.com>
To: Fabio Estevam <festevam@...il.com>
Cc: linux-kernel@...r.kernel.org,  Russell King <linux@...linux.org.uk>,
  Ulf Hansson <ulf.hansson@...aro.org>,  Shawn Guo <shawnguo@...nel.org>,
  "Rob Herring (Arm)" <robh@...nel.org>,  Angelo Dureghello
 <angelo@...nel-space.org>
Subject: Re: ARM iMX6sx board fails to boot with kernel 6.17

Hi Fabio,

Fabio Estevam <festevam@...il.com> writes:

> Hi Sergey,
>
> On Sat, Oct 11, 2025 at 5:57 PM Sergey Organov <sorganov@...il.com>
> wrote:
>
>> I'm not familiar with the code and can't figure what exactly I'm
>> expected to check. Could you please prepare a patch, and I'll be
>> happy to apply and check it.
>
> Here is a patch you can try.
>
> It's not a formal patch yet, as it needs to be split.

As I've already reported, this patch unfortunately doesn't solve my
issue, but then things got even more "interesting".

Before I've said that latest kernel branch lf-6.12.y on
https://github.com/nxp-imx/linux-imx does not have the 816978f83b
commit, but yesterday I've found it does include similar change though
with different commit message and without any reference to the original
commit (that's why I missed it):

https://github.com/nxp-imx/linux-imx/commit/3f127cc4f5f0f1c8563390c4db7727fcb5735aa9

Now, this commit does *not* solve my problem either. I.e., lf-6.12.y
still hangs on my board. I even tried to cherry-pick the original
816978f83b on top of this, and all the conflicts I got look formal
rather than functional, leaving code unchanged after resolution, so this
commit is in fact almost perfect cherry-pick of the original 816978f83b
that did solve my problem on the imx_4.9.11_1.0.0_ga branch of that
repository.

Yet another thing I figured that it's unlikely powering problem, as both
3.3 and 1.8 are still there on eMMC when the board hangs. Clocks are
most probable suspect then.

I'm going to dig into imx_4.9.11_1.0.0_ga branch again more carefully to
try to figure what's going on, and what actually either fixes or
work-arounds the problem at hand.

-- Sergey Organov