Kukjin, On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@xxxxxxxxxx> wrote: > Kukjin Kim <kgene@xxxxxxxxxx> writes: > >> Kevin Hilman wrote: >>> >>> From: Kevin Hilman <khilman@xxxxxxxxxx> >>> >>> 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@xxxxxxxxxxx>, >>> Cc: Javier Martinez Canillas <javier.martinez@xxxxxxxxxxxxxxx>, >>> Cc: Sachin Kamat <sachin.kamat@xxxxxxxxxxx>, >>> Cc: Doug Anderson <dianders@xxxxxxxxxxxx>, >>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx>, >>> Cc: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>, >>> Cc: Tushar Behera <tushar.behera@xxxxxxxxxx>, >>> Cc: stable@xxxxxxxxxxxxxxx # v3.17+ >>> Signed-off-by: Kevin Hilman <khilman@xxxxxxxxxx> >>> --- >>> 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. Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. What is the status of $SUBJECT patch? >> 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. Is anyone at Samsung actually looking into these MCPM issues? Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |