[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1509828560.21320.19.camel@toradex.com>
Date: Sat, 4 Nov 2017 20:49:22 +0000
From: Marcel Ziswiler <marcel.ziswiler@...adex.com>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"digetx@...il.com" <digetx@...il.com>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"rafael.j.wysocki@...el.com" <rafael.j.wysocki@...el.com>
CC: "thierry.reding@...il.com" <thierry.reding@...il.com>,
"mirq-linux@...e.qmqm.pl" <mirq-linux@...e.qmqm.pl>
Subject: Re: T20 Cpuidle Freeze
On Fri, 2017-11-03 at 21:52 +0300, Dmitry Osipenko wrote:
> I haven't seen any problems with the cpuidle on next and 4.14-rc7
> works fine.
>
> # cat /sys/devices/system/cpu/cpu[0-1]/cpuidle/state[0-1]/usage
> 162283
> 32905
> 254669
> 32905
>
> # cat /sys/devices/system/cpu/cpu[0-1]/cpuidle/state[0-1]/time
> 436981763
> 2110484666
> 458260707
> 2121781516
>
> # uptime
> 18:50:24 up 44 min, 1 user, load average: 0.15, 0.08, 0.07
OK, thanks. Good to know.
> It could be that cpuidle unmasks some other issue on the Colibri.
Yes, that's also my thinking.
What hardware did you run this on?
Does your kernel configuration differ from the stock tegra_defconfig I used?
What exact device tree source are you using (or just stock)?
Maybe the compiler version you are using could also have some influence?
If you have any additional suggestions on what else could be relevant please let me know.
Powered by blists - more mailing lists