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]
Date:   Sat, 28 Mar 2020 08:18:42 -0300
From:   Fabio Estevam <festevam@...il.com>
To:     Adam Ford <aford173@...il.com>
Cc:     arm-soc <linux-arm-kernel@...ts.infradead.org>,
        Adam Ford-BE <aford@...conembedded.com>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        NXP Linux Team <linux-imx@....com>,
        Anson Huang <Anson.Huang@....com>,
        devicetree <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: i.MX8MN Errors on 5.6-RC7

Hi Adam,

On Fri, Mar 27, 2020 at 11:50 PM Adam Ford <aford173@...il.com> wrote:
>
> I am getting a few errors on the i.MX8MN:
>
> [    0.000368] Failed to get clock for /timer@...a0000
> [    0.000380] Failed to initialize '/timer@...a0000': -22
> [    7.203447] caam 30900000.caam: Failed to get clk 'ipg': -2
> [    7.334741] caam 30900000.caam: Failed to request all necessary clocks
> [    7.438651] caam: probe of 30900000.caam failed with error -2
> [    7.854193] imx-cpufreq-dt: probe of imx-cpufreq-dt failed with error -2
>
> I was curious to know if anyone else is seeing similar errors.  I
> already submitted a proposed fix for a DMA timeout (not shown here)
> which matched work already done on i.MX8MQ and i.MX8MM.
>
> I am not seeing huge differences between 8MM and 8MN in the nodes
> which address the timer, caam or imx-cpufreq-dt.
>
> If anyone has any suggestions, I'd love to try them.

I don't have access to a i.MX8MN board at the moment, but I am
wondering if the errors could be AT-F related.

Which version do you use? Could you try
https://source.codeaurora.org/external/imx/imx-atf/log/?h=imx_5.4.3_2.0.0
?

Regards,

Fabio Estevam

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ