* Vlastimil Babka <vbabka@xxxxxxx> [170905 13:29]:
> On 09/05/2017 10:13 PM, Tony Lindgren wrote:
> > * Pavel Machek <pavel@xxxxxx> [170903 13:38]:
> >> Hi!
> >>
> >> It compiles ok, but it hangs on boot; black screen, so sometime before
> >> display is initialized.
> >
> > Thanks for reporting it. Based on git bisect, the regression causing
> > commit is 9caf25f996e8 ("mm/cma: manage the memory of the CMA area
> > by using the ZONE_MOVABLE"). With this path applied, booting hangs
> > with an error in omap3_save_secure_ram_context() after a call to
> > _omap_save_secure_sram() that calls the related assembly code
> > save_secure_ram_context.
> >
> > However, looks like there is also some other commit causing issue.
> >
> > Just reverting 9caf25f996e8 on Linux next causes the oops below.
> >
> > Anybody got ideas why this now happens?
>
> I know that there are other two patches from the same series depending
> on the one you reverted:
>
> mm/cma: remove ALLOC_CMA
> ARM: CMA: avoid double mapping to the CMA area if CONFIG_HIGHMEM = y
>
> I'm guessing you need to revert all to have something consistent to test.
Thanks, yes reverting all three in next makes things boot
for me again.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
