Kukjin Kim [off-list ref] writes:

Kevin Hilman wrote:

quoted

From: Kevin Hilman <redacted>

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 <redacted>,
Cc: Javier Martinez Canillas <redacted>,
Cc: Sachin Kamat <redacted>,
Cc: Doug Anderson <dianders@chromium.org>,
Cc: Bartlomiej Zolnierkiewicz <redacted>,
Cc: Krzysztof Kozlowski <redacted>,
Cc: Tushar Behera <redacted>,
Cc: stable at vger.kernel.org # v3.17+
Signed-off-by: Kevin Hilman <redacted>
---
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