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: <20171025212806.GA21504@atomide.com>
Date:   Wed, 25 Oct 2017 14:28:07 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Pavel Machek <pavel@....cz>
Cc:     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,
        clayton@...ftyguy.net, martijn@...xit.nl,
        sakari.ailus@...ux.intel.com, filip.matijevic.pz@...il.com
Subject: Re: 4.13 (and probably all recent) kernels refuse to boot on one
 Nokia N950, work or another

* Pavel Machek <pavel@....cz> [171025 13:36]:
> Hi!
> 
> ...hardware should be identical. 3.5.3-nemo kernel seems to work on
> both. 4.13-rc2 with display and clock patches boots on phone "S", but
> does not on phone "P"; nothing nothing is received on serial port.
> 
> There is some difference in the bootloaders: S's bootloader provides
> lots of debug info, P's is silent. R&D settings do _not_ have
> influence on bootloader. We know P's serial works, as 3.5.3 kernel
> prints "Uncompressing linux...booting" there.
> 
> I'll need to return "S" phone and serial cable tommorow. If you have
> any ideas, let me know.

If you get nothing out of the uart, chances are the pins are
not muxed for the uart in nolo and maybe kernel dts is missing the
pinctrl entries for uart?

Also try booting with mem=512M@...0000000 or 256M or 768M. Maybe the
memory is different size or partially broken?

Regards,

Tony

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ