[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5Aoj9pUpMdqVTG2pOUBUpnHsxA-Kduhia7_EJZvdEGjwQ@mail.gmail.com>
Date: Mon, 2 Dec 2019 10:49:29 -0300
From: Fabio Estevam <festevam@...il.com>
To: Igor Plyatov <plyatov@...il.com>
Cc: Zhang Rui <rui.zhang@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Amit Kucheria <amit.kucheria@...durent.com>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>, linux-pm@...r.kernel.org,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Issue with imx_get_temp()
Hi Igor,
On Mon, Dec 2, 2019 at 10:44 AM Igor Plyatov <plyatov@...il.com> wrote:
>
> Dear all,
>
> please look at back-trace below. It happens on Freescale i.MX6 Quad.
>
> Found a few of those during power on/off stress test in the climate chamber:
>
> [ 0.657596] ------------[ cut here ]------------
> [ 0.657626] WARNING: CPU: 3 PID: 150 at /home/geosig/development/oe-core-toradex-cr7/build/tmp-glibc/work-shared/cr7/kernel-source/kernel/irq/chip.c:242 __irq_startup+0x94/0xa8
> [ 0.657630] Modules linked in:
> [ 0.657643] CPU: 3 PID: 150 Comm: kworker/3:1 Not tainted 5.1.1 #1
Are you able to reproduce this issue with a 5.4.1 kernel?
Thanks
Powered by blists - more mailing lists