From: Sergey Organov <sorganov@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Ulf Hansson <ulf.hansson@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
"Rob Herring (Arm)" <robh@kernel.org>,
Angelo Dureghello <angelo@kernel-space.org>
Subject: Re: ARM iMX6sx board fails to boot with kernel 6.17
Date: Thu, 09 Oct 2025 19:29:59 +0300 [thread overview]
Message-ID: <87v7ko11iw.fsf@osv.gnss.ru> (raw)
In-Reply-To: <CAOMZO5AFer_Yy20fqD9oVSNVPR2ZvvwYbrkSuj7eFgS_uMJC3A@mail.gmail.com> (Fabio Estevam's message of "Thu, 9 Oct 2025 12:50:46 -0300")
Hi Fabio,
Fabio Estevam <festevam@gmail.com> writes:
> Hi Sergey,
>
> On Thu, Oct 9, 2025 at 11:46 AM Sergey Organov <sorganov@gmail.com> wrote:
>
>> > I tried booting 6.17 on an imx6sx-sdb board and it booted
>> > successfully:
>>
>> Now after further investigations of the issue I find that success
>> a bit surprising.
>>
>> I've found that my problem is cured by a commit in
>>
>> https://github.com/nxp-imx/linux-imx
>>
>> that works-around an issue that looks like imx6sx generic problem, and
>> should probably cause troubles on imx6sx-sdb board as well, but doesn't?
>> The commit is:
>>
>> commit 65cf3a49ab15cdbbede3c97fd6bba731a3cd366f
>> Author: Anson Huang <b20788@freescale.com>
>> AuthorDate: Tue Aug 18 15:53:54 2015 +0800
>> Commit: Octavian Purdila <octavian.purdila@nxp.com>
>> CommitDate: Thu Feb 23 14:21:42 2017 +0200
>>
>> MLK-11375-2 ARM: imx: disable cpuidle for imx6sx
>>
>> i.MX6SX CPUIdle with ARM core power down has issue
>> and cause system hang during kernel boot up, disable
>> it for now and will enable it when busfreq driver
>> is ready.
>>
>> Later (by the DAG, not by date) on the same imx_4.9.11_1.0.0_ga
>> branch at that repo, there is:
>>
>> commit 816978f83b1d8dd6ce3bd5dd62223dbfdf74bdd3
>> Author: Anson Huang <b20788@freescale.com>
>> AuthorDate: Mon Oct 20 16:16:20 2014 +0800
>> Commit: Octavian Purdila <octavian.purdila@nxp.com>
>> CommitDate: Thu Feb 23 14:21:42 2017 +0200
>>
>> MLK-9708 arm: imx: add low power idle support for i.mx6sx
>>
>> that effectively reverts the aforementioned commit while adding a lot of
>> other stuff. The resulting kernel also boots fine on my hardware.
>>
>> Curiously enough, neither of these commits are there in the latest
>> branch lf-6.12.y there (and that kernel hangs on my board as well.)
>>
>> Provided the latter commit is indeed the right fix for imx6sx support in
>> the kernel, what's the procedure to get it to the mainstream Linux
>> kernel?
>
> It seems that your observation matches what Angelo (added on Cc)
> reported a long time ago:
>
> https://community.nxp.com/t5/i-MX-Processors/imx6sx-kernel-hangs-at-rootfs-mount/td-p/964920
>
> I'd like to know if the bootloader version plays a role in the
> different behavior that we see on the imx6sx-sdb versus your board.
>
> I used U-Boot 2024.07 on my imx6sx-sdb. Which version did you use? Is
> it based on an old NXP U-Boot tree?
>
> Does using a recent bootloader make the hang disappear?
Uhh... U-Boot is very old and is heavily modified anyway. I figure our
local history starts at:
rel_imx_4.1.33_7ulp_beta
commit 43bff39513ae89c476751caff427b9855af78f7e
Author: Ye Li <ye.li@nxp.com>
Date: Fri Apr 14 13:44:48 2017 +0800
MLK-14693 mx7ulp: Change PLL rate calculation to avoid div 0
that looks like NXP tree to me indeed, likely taken once upon a time
from:
https://gitlab.com/jcgit/uboot-imx.git
that was a mirror of original NXP repository
git://git.freescale.com/imx/uboot-imx.git
That said, I wanted to get to recent kernel using working u-boot, then
maybe try to upgrade u-boot as well, but maybe even not. No reason as of
yet, especially as it's difficult for me to recover from a brick state
should boot-loader fail.
-- Sergey Organov
next prev parent reply other threads:[~2025-10-09 16:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 15:49 ARM iMX6sx board fails to boot with kernel 6.17 Sergey Organov
2025-09-30 19:09 ` Fabio Estevam
2025-09-30 19:11 ` Fabio Estevam
2025-10-06 20:11 ` Sergey Organov
2025-10-06 20:20 ` Fabio Estevam
2025-10-06 21:22 ` Sergey Organov
2025-10-07 2:05 ` Fabio Estevam
2025-10-07 11:35 ` Sergey Organov
2025-10-07 15:19 ` Ulf Hansson
2025-10-07 21:17 ` Sergey Organov
2025-10-07 21:29 ` Fabio Estevam
2025-10-07 21:44 ` Fabio Estevam
2025-10-08 12:53 ` Sergey Organov
2025-10-08 17:04 ` Sergey Organov
2025-10-01 20:04 ` Sergey Organov
2025-10-02 0:45 ` Fabio Estevam
2025-10-09 14:46 ` Sergey Organov
2025-10-09 15:50 ` Fabio Estevam
2025-10-09 16:29 ` Sergey Organov [this message]
2025-10-09 17:26 ` Fabio Estevam
2025-10-09 21:51 ` Sergey Organov
2025-10-09 22:40 ` Fabio Estevam
2025-10-10 14:59 ` Sergey Organov
2025-10-10 15:14 ` Fabio Estevam
2025-10-11 20:57 ` Sergey Organov
2025-10-14 0:45 ` Fabio Estevam
2025-10-14 12:04 ` Sergey Organov
2025-10-20 21:30 ` Sergey Organov
2025-10-27 14:39 ` Sergey Organov
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=87v7ko11iw.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=angelo@kernel-space.org \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.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