linux-kernel - Re: n900 in next-20170901

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170905203240.GF5024@atomide.com>
Date:   Tue, 5 Sep 2017 13:32:44 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Vlastimil Babka <vbabka@...e.cz>
Cc:     Pavel Machek <pavel@....cz>, pali.rohar@...il.com, sre@...nel.org,
        kernel list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-omap@...r.kernel.org, khilman@...nel.org,
        aaro.koskinen@....fi, ivo.g.dimitrov.75@...il.com,
        patrikbachan@...il.com, serge@...lyn.com, abcloriens@...il.com,
        Joonsoo Kim <iamjoonsoo.kim@....com>,
        "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Russell King <linux@...linux.org.uk>
Subject: Re: n900 in next-20170901

* Vlastimil Babka <vbabka@...e.cz> [170905 13:29]:
> On 09/05/2017 10:13 PM, Tony Lindgren wrote:
> > * Pavel Machek <pavel@....cz> [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