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] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o6qjaiz7.fsf@osv.gnss.ru>
Date: Mon, 06 Oct 2025 23:11:24 +0300
From: Sergey Organov <sorganov@...il.com>
To: Fabio Estevam <festevam@...il.com>
Cc: linux-kernel@...r.kernel.org,  Ulf Hansson <ulf.hansson@...aro.org>,
  Shawn Guo <shawnguo@...nel.org>,  "Rob Herring (Arm)" <robh@...nel.org>,
  Anson Huang <Anson.Huang@....com>
Subject: Re: ARM iMX6sx board fails to boot with kernel 6.17

Hi Fabio,

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

> On Tue, Sep 30, 2025 at 4:09 PM Fabio Estevam <festevam@...il.com> wrote:
>
>> I tried booting 6.17 on an imx6sx-sdb board and it booted successfully:
>
> I forgot to say that I have used the imx_v6_v7_defconfig.

I've checked that I end-up with the same DTB as you sent me off-list for
this configuration, so at least this part seems to work fine on my side.

I also tried the imx_v6_v7_defconfig - based kernel on my board
(obviously with my custom DTB), and the kernel still doesn't boot.

Further, I've found that it's enough to disable CONFIG_REGULATOR_ANATOP
in my custom kernel config to get kernel to see eMMC card, and then
mount it as root file-system.

I still fail to see what I do (or don't do) in my DTS (or kernel config)
to confuse the kernel, and how to figure that out. Any ideas?

-- Sergey Organov

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ