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