From: Kevin Hilman <khilman@kernel.org>
To: Kukjin Kim <kgene@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org,
'Javier Martinez Canillas' <javier.martinez@collabora.co.uk>,
'Sachin Kamat' <sachin.kamat@samsung.com>,
'Doug Anderson' <dianders@chromium.org>,
'Bartlomiej Zolnierkiewicz' <b.zolnierkie@samsung.com>,
'Krzysztof Kozlowski' <k.kozlowski@samsung.com>,
'Tushar Behera' <tushar.behera@linaro.org>
Subject: Re: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable
Date: Mon, 10 Nov 2014 11:35:23 -0800 [thread overview]
Message-ID: <7hegtaq26c.fsf@deeprootsystems.com> (raw)
In-Reply-To: <000e01cffb39$5ef0a2d0$1cd1e870$@kernel.org> (Kukjin Kim's message of "Sat, 08 Nov 2014 18:50:04 +0900")
Kukjin Kim <kgene@kernel.org> writes:
> Kevin Hilman wrote:
>>
>> From: Kevin Hilman <khilman@linaro.org>
>>
>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts
>> during boot testing, causing various userspace startup failures.
>>
>> Disable until it has gotten more testing.
>>
>> Cc: Kukjin Kim <kgene.kim@samsung.com>,
>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
>> Cc: Sachin Kamat <sachin.kamat@samsung.com>,
>> Cc: Doug Anderson <dianders@chromium.org>,
>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
>> Cc: Tushar Behera <tushar.behera@linaro.org>,
>> Cc: stable@vger.kernel.org # v3.17+
>> Signed-off-by: Kevin Hilman <khilman@linaro.org>
>> ---
>> This has been reported by a few people[1], but not investigated or fixed, so it's
>> time to disable this feature until it can be fixed.
>>
> Hi Kevin,
>
> Yeah I agree with your opinion.
>
> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will
> be shown in -next in this weekend.
Which of the recently queued patches are expected to address the
imprecise abort issue? I'd be happy to test them out.
> Anyway let me apply this into -fixes and
> then let's enable after test its functionality in -next in a couple of days.
Yes, I think this needs to be applied until these aborts are understood
and fixed.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable
Date: Mon, 10 Nov 2014 11:35:23 -0800 [thread overview]
Message-ID: <7hegtaq26c.fsf@deeprootsystems.com> (raw)
In-Reply-To: <000e01cffb39$5ef0a2d0$1cd1e870$@kernel.org> (Kukjin Kim's message of "Sat, 08 Nov 2014 18:50:04 +0900")
Kukjin Kim <kgene@kernel.org> writes:
> Kevin Hilman wrote:
>>
>> From: Kevin Hilman <khilman@linaro.org>
>>
>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts
>> during boot testing, causing various userspace startup failures.
>>
>> Disable until it has gotten more testing.
>>
>> Cc: Kukjin Kim <kgene.kim@samsung.com>,
>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
>> Cc: Sachin Kamat <sachin.kamat@samsung.com>,
>> Cc: Doug Anderson <dianders@chromium.org>,
>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
>> Cc: Tushar Behera <tushar.behera@linaro.org>,
>> Cc: stable at vger.kernel.org # v3.17+
>> Signed-off-by: Kevin Hilman <khilman@linaro.org>
>> ---
>> This has been reported by a few people[1], but not investigated or fixed, so it's
>> time to disable this feature until it can be fixed.
>>
> Hi Kevin,
>
> Yeah I agree with your opinion.
>
> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will
> be shown in -next in this weekend.
Which of the recently queued patches are expected to address the
imprecise abort issue? I'd be happy to test them out.
> Anyway let me apply this into -fixes and
> then let's enable after test its functionality in -next in a couple of days.
Yes, I think this needs to be applied until these aborts are understood
and fixed.
Thanks,
Kevin
next prev parent reply other threads:[~2014-11-10 19:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 22:59 [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable Kevin Hilman
2014-10-31 22:59 ` Kevin Hilman
2014-11-08 9:50 ` Kukjin Kim
2014-11-08 9:50 ` Kukjin Kim
2014-11-10 19:35 ` Kevin Hilman [this message]
2014-11-10 19:35 ` Kevin Hilman
2014-11-24 19:51 ` Kevin Hilman
2014-11-24 19:51 ` Kevin Hilman
2014-11-25 0:25 ` Olof Johansson
2014-11-25 0:25 ` Olof Johansson
2014-11-25 1:35 ` Kevin Hilman
2014-11-25 1:35 ` Kevin Hilman
2014-11-25 1:37 ` Olof Johansson
2014-11-25 1:37 ` Olof Johansson
2014-11-25 1:38 ` Olof Johansson
2014-11-25 1:38 ` Olof Johansson
2014-11-25 1:50 ` Kukjin Kim
2014-11-25 1:50 ` Kukjin Kim
2014-11-25 3:20 ` Kevin Hilman
2014-11-25 3:20 ` Kevin Hilman
2014-11-25 6:01 ` Abhilash Kesavan
2014-11-25 6:01 ` Abhilash Kesavan
2014-11-26 1:00 ` Kevin Hilman
2014-11-26 1:00 ` Kevin Hilman
2014-11-26 16:58 ` Abhilash Kesavan
2014-11-26 16:58 ` Abhilash Kesavan
2014-11-26 17:56 ` Kevin Hilman
2014-11-26 17:56 ` Kevin Hilman
2014-11-26 18:11 ` Kukjin Kim
2014-11-26 18:11 ` Kukjin Kim
2014-11-26 18:41 ` Nicolas Pitre
2014-11-26 18:41 ` Nicolas Pitre
2014-11-27 16:51 ` Abhilash Kesavan
2014-11-27 16:51 ` Abhilash Kesavan
2014-11-27 17:06 ` Nicolas Pitre
2014-11-27 17:06 ` Nicolas Pitre
2014-11-28 14:41 ` Abhilash Kesavan
2014-11-28 14:41 ` Abhilash Kesavan
2014-11-27 18:57 ` Sudeep Holla
2014-11-27 18:57 ` Sudeep Holla
2014-11-25 8:47 ` Krzysztof Kozlowski
2014-11-25 8:47 ` Krzysztof Kozlowski
2014-11-25 9:07 ` Krzysztof Kozlowski
2014-11-25 9:07 ` Krzysztof Kozlowski
2014-11-25 2:13 ` Kevin Hilman
2014-11-25 2:13 ` Kevin Hilman
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=7hegtaq26c.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=dianders@chromium.org \
--cc=javier.martinez@collabora.co.uk \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sachin.kamat@samsung.com \
--cc=tushar.behera@linaro.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.