public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>
Cc: "digetx@gmail.com" <digetx@gmail.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	"mirq-linux@rere.qmqm.pl" <mirq-linux@rere.qmqm.pl>
Subject: T20 Cpuidle Freeze
Date: Fri, 3 Nov 2017 13:07:05 +0000	[thread overview]
Message-ID: <1509714423.21320.11.camel@toradex.com> (raw)

Hi Rafael, dear community

One of our customers reported seeing freezes when running the LTS Linux
kernel 4.9.x on our Toradex Colibri T20 modules [1]. I was able to
reproduce a complete SoC lock-up after a few minutes also running the
latest 4.14-rc7 while LTS 4.4.x seemed to run stable.

Having attempted a multi-level bisection points towards the following
first bad commit:

9c4b2867ed7c8c8784dd417ffd16e705e81eb145

cpuidle: menu: Fix menu_select() for CPUIDLE_DRIVER_STATE_START == 0

Unfortunately as drivers/cpuidle/governors/menu.c has gotten further
edits since it seems not trivial to just revert it.

However I found out that it indeed has to do with CPU idle as when I
did disable the CONFIG_CPU_IDLE Linux kernel configuration option also
LTS 4.9.59 as well as latest 4.14-rc7 run now stable overnight.

Does anybody have any clue what exactly may be happening and/or why
cpuidle may not run stable on T20? Or is everybody always just
disabling cpuidle on T20 anyway?

Thanks!

[1] https://www.toradex.com/community/questions/16838/actual-lts-kernel
-49-on-colibri-t20.html

Best regards - Mit freundlichen Grüssen - Meilleures salutations

Marcel Ziswiler
Platform Manager Embedded Linux

Toradex AG
Altsagenstrasse 5 | 6048 Horw/Luzern | Switzerland | T: +41 41 500 48 00
(main line) | Direct: +41 41 500 48 10

             reply	other threads:[~2017-11-03 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 13:07 Marcel Ziswiler [this message]
2017-11-03 18:52 ` T20 Cpuidle Freeze Dmitry Osipenko
2017-11-04 20:49   ` Marcel Ziswiler
2017-11-05 13:16     ` Dmitry Osipenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1509714423.21320.11.camel@toradex.com \
    --to=marcel.ziswiler@toradex.com \
    --cc=digetx@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=rafael.j.wysocki@intel.com \
    --cc=thierry.reding@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox