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: <20171026072113.z5bqer7os62ckf3z@pali>
Date:   Thu, 26 Oct 2017 09:21:13 +0200
From:   Pali Rohár <pali.rohar@...il.com>
To:     Pavel Machek <pavel@....cz>
Cc:     Filip Matijević <filip.matijevic.pz@...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, tony@...mide.com, khilman@...nel.org,
        aaro.koskinen@....fi, ivo.g.dimitrov.75@...il.com,
        patrikbachan@...il.com, serge@...lyn.com, abcloriens@...il.com,
        clayton@...ftyguy.net, martijn@...xit.nl,
        sakari.ailus@...ux.intel.com
Subject: Re: 4.13 (and probably all recent) kernels refuse to boot on one
 Nokia N950, work or another

On Thursday 26 October 2017 09:08:15 Pavel Machek wrote:
> On Thu 2017-10-26 08:25:02, Filip Matijević wrote:
> > Last time I couldn't get output on serial I used CONFIG_DEBUG_LL,
> > CONFIG_DEBUG_OMAP3UART3, CONFIG_EARLY_PRINTK... and ignore_loglevel
> > earlyprintk kernel params to get output early enough - I guess you
> > already tried that.
> 
> I realized I'm not getting output from the decompessor (even on "S"
> machine), and enabled that.

That is because you have not enabled those EARLY PRINK or DEBUG LL.
Similar thing is needed for N900 and IIRC in some of my linux-n900
branches I have config for it. Plus it needs patching some arch/arm
source files to make it working.

> But I'm _still_ not getting any output on decompressor... early
> printing works ok on "S" but not on "P".

I guess there can be either problem with memory mapping and RAM size or
with OMAP HS mode?

-- 
Pali Rohár
pali.rohar@...il.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ