From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: exynos4: cpu hotplug + cpuidle/AFTR broken
Date: Tue, 01 Apr 2014 14:49:17 +0200 [thread overview]
Message-ID: <533AB5CD.7080209@linaro.org> (raw)
In-Reply-To: <533AB128.7050208@samsung.com>
On 04/01/2014 02:29 PM, Tomasz Figa wrote:
>
>
> On 01.04.2014 14:16, Daniel Lezcano wrote:
>> On 04/01/2014 01:22 PM, Tomasz Figa wrote:
>>> Hi Daniel,
>>>
>>> On 01.04.2014 12:43, Daniel Lezcano wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I tried the v3.14 kernel and unplugged the cpu1. That leads to a kernel
>>>> hang without any trace.
>>>>
>>>> If I disable the cpuidle AFTR state through sysfs before unplugging
>>>> cpu1, it works well.
>>>>
>>>> I reproduced the issue on v3.14, v3.13, v3.12, v3.11
>>>>
>>>> v3.10 works fine.
>>>
>>> Could you try to reproduce the same issue on linux-next? Some of PM
>>> issues on Exynos should be patches there.
>>
>> Tested on linux-next. Works fine.
>
> Great, thanks.
>
>>
>> Do you have an idea of the patch which have fixed the issue ? In order
>> to backport it the kernels mentioned above.
>
> Most likely it's this one:
>
> 61557b8bac ARM: EXYNOS: Do not resume l2x0 if not enabled before suspend
Confirmed.
This patch fixes the issue.
Will you send the fix for the different kernel v3.14, v3.13, v3.12 ?
(v3.11 is EOL).
Thanks !
-- Daniel
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2014-04-01 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 10:43 exynos4: cpu hotplug + cpuidle/AFTR broken Daniel Lezcano
2014-04-01 11:04 ` Krzysztof Kozlowski
2014-04-01 11:51 ` Daniel Lezcano
2014-04-01 11:22 ` Tomasz Figa
2014-04-01 12:16 ` Daniel Lezcano
2014-04-01 12:29 ` Tomasz Figa
2014-04-01 12:49 ` Daniel Lezcano [this message]
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=533AB5CD.7080209@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).