From: daniel.lezcano@linaro•org (Daniel Lezcano)
To: linux-arm-kernel@lists•infradead.org
Subject: [Bug] ARM: mxs: STI: console can't wake up from freeze
Date: Sat, 5 Nov 2016 14:00:34 +0100 [thread overview]
Message-ID: <20161105130034.GG15759@mai> (raw)
In-Reply-To: <122295766.159553.9867e3e7-5710-4844-a098-6f44bd852a6d.open-xchange@email.1und1.de>
On Sat, Nov 05, 2016 at 01:01:26PM +0100, Stefan Wahren wrote:
[?... ]
> > > CONFIG_SUSPEND=y
> > > CONFIG_SUSPEND_FREEZER=y
> > > CONFIG_PM=y
> > > CONFIG_CPU_IDLE is not set
> >
> > hmmm, why not have CONFIG_CPU_IDLE set?
>
> I'm using mxs_defconfig which doesn't select the ARM CPU idle. Is this
> necessary?
Very likely :) suspend_freezer and cpuidle are tied together.
Moreover, while reading the code, it appears without CONFIG_CPU_IDLE the
function cpuidle_idle_call is constantly failing, ending up by having the
cpu looping again and again in the idle loop. The function stubs return
-ENODEV in the cpuidle's header when CONFIG_CPU_IDLE is not set.
If I'm not wrong the traces should show the cpu actually does never go
to suspend. As soon as it enters the state, it should exit immediately
without an interrupt event.
Probably there is an inconsistent configuration leaving the kernel with
a strange wakeup condition or a race with the short the suspend/resume
cycle delay.
First test would be to enable CONFIG_CPU_IDLE.
If it is confirmed, it would be nice to feed bugzilla.
next prev parent reply other threads:[~2016-11-05 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 9:19 [Bug] ARM: mxs: STI: console can't wake up from freeze Stefan Wahren
2016-10-23 13:31 ` Russell King - ARM Linux
2016-10-29 11:44 ` Stefan Wahren
2016-10-31 16:17 ` Russell King - ARM Linux
2016-10-31 19:54 ` Stefan Wahren
2016-11-01 9:23 ` Russell King - ARM Linux
2016-11-05 11:07 ` Stefan Wahren
2016-11-05 11:39 ` Zhang Rui
2016-11-05 12:01 ` Stefan Wahren
2016-11-05 13:00 ` Daniel Lezcano [this message]
2016-11-05 15:28 ` Stefan Wahren
2016-11-05 18:05 ` Russell King - ARM Linux
2016-11-06 10:20 ` Stefan Wahren
2016-11-06 14:55 ` Daniel Lezcano
2016-11-06 18:31 ` Stefan Wahren
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=20161105130034.GG15759@mai \
--to=daniel.lezcano@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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