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: <CAFBinCBe3LhN+3beovFVuWPpe3pDF5P1wSt7nPjm=ykRAx4zzQ@mail.gmail.com>
Date: Sun, 21 Sep 2025 14:21:28 +0200
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: Mark Brown <broonie@...nel.org>
Cc: Jerome Brunet <jbrunet@...libre.com>, Neil Armstrong <neil.armstrong@...aro.org>, 
	Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, 
	Kevin Hilman <khilman@...libre.com>, linux-amlogic@...ts.infradead.org, 
	linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/26] clk: amlogic: clock controllers clean-up and factorisation

Hi Mark,

On Sun, Sep 21, 2025 at 1:25 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Wed, Jul 02, 2025 at 05:25:58PM +0200, Jerome Brunet wrote:
> > The work on this patchset started with the submission of the Amlogic t7
> > peripheral clock controller [1]. This controller is fairly similar to
> > existing controllers. Once again, it redefines the peripheral clock macro,
> > the probe function and composite clock helpers, even if it is almost the
> > same as in other controllers. This code duplication trend has been going on
> > for too long and now is the time to properly address the problem.
>
> Friday's -next breaks the boot for me on the Libretch Alta.  The system
> doesn't show any output on the console unfortunately:
>
>    https://lava.sirena.org.uk/scheduler/job/1853204#L1606
>
> Unfortunately earlycon isn't turned on, I'll try to do so at tomorrow or
> Tuesday.
>
> A bisect points to the patch 4c4e17f27013 ("clk: amlogic: naming
> consistency alignment") which looks like it's a squash of several of the
> patches here.  Due to issues with the bootloader it could potentially be
> an adjacent commit but this looks suspiciously relevant.  Bisect log, my
> infrastructure does retry the boot a lot on these boards so even if the
> final error is a bootloader issue there will likely have been boots that
> start the kernel:
A few days ago Marek reported problems on an Odroid-N2 and provided a fix: [0]
It's not queued up for -next yet.

Please give Marek's patch a try


[0] https://lore.kernel.org/linux-amlogic/175834437006.4354.11933545174004616373@lazor/T/#m29128b0acec2db62d45971d94a1c38fedc8493a0

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ