From: Tomasz Figa <t.figa@samsung.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-samsung-soc@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: exynos4: cpu hotplug + cpuidle/AFTR broken
Date: Tue, 01 Apr 2014 13:22:34 +0200 [thread overview]
Message-ID: <533AA17A.1090405@samsung.com> (raw)
In-Reply-To: <533A9849.1080402@linaro.org>
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.
Best regards,
Tomasz
WARNING: multiple messages have this Message-ID (diff)
From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: exynos4: cpu hotplug + cpuidle/AFTR broken
Date: Tue, 01 Apr 2014 13:22:34 +0200 [thread overview]
Message-ID: <533AA17A.1090405@samsung.com> (raw)
In-Reply-To: <533A9849.1080402@linaro.org>
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.
Best regards,
Tomasz
next prev parent reply other threads:[~2014-04-01 11:22 UTC|newest]
Thread overview: 14+ 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 10:43 ` Daniel Lezcano
2014-04-01 11:04 ` Krzysztof Kozlowski
2014-04-01 11:04 ` Krzysztof Kozlowski
2014-04-01 11:51 ` Daniel Lezcano
2014-04-01 11:51 ` Daniel Lezcano
2014-04-01 11:22 ` Tomasz Figa [this message]
2014-04-01 11:22 ` Tomasz Figa
2014-04-01 12:16 ` Daniel Lezcano
2014-04-01 12:16 ` Daniel Lezcano
2014-04-01 12:29 ` Tomasz Figa
2014-04-01 12:29 ` Tomasz Figa
2014-04-01 12:49 ` Daniel Lezcano
2014-04-01 12:49 ` Daniel Lezcano
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=533AA17A.1090405@samsung.com \
--to=t.figa@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.