Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751435AbdIONSV (ORCPT ); Fri, 15 Sep 2017 09:18:21 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:55462 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751207AbdIONSU (ORCPT ); Fri, 15 Sep 2017 09:18:20 -0400 Date: Fri, 15 Sep 2017 15:18:18 +0200 From: Pavel Machek To: Tony Lindgren Cc: Joonsoo Kim , pali.rohar@gmail.com, sre@kernel.org, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com, "Aneesh Kumar K.V" , Vlastimil Babka , Andrew Morton , Stephen Rothwell , Russell King Subject: Re: n900 in next-20170901 Message-ID: <20170915131817.GA19486@amd> References: <20170903203737.GA12475@amd> <20170905201314.GE5024@atomide.com> <20170905233241.GA19231@js1304-P5Q-DELUXE> <20170906133057.GH5024@atomide.com> <20170907073038.GA2111@js1304-P5Q-DELUXE> <20170907161650.GP5024@atomide.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <20170907161650.GP5024@atomide.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1618 Lines: 49 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > After commit 9caf25f996e8, user for CMA memory should use to check > > PageHighmem in order to get proper virtual address of the page. If > > someone doesn't use it, it is possible to use wrong virtual address > > and it then causes the use of wrong physical address. > > CONFIG_DEBUG_VIRTUAL would catch this case. >=20 > OK, no extra output of current next with CONFIG_DEBUG_VIRTUAL=3Dy. > Booting of n900 hangs with just the same error: >=20 > save_secure_sram() returns 0000ff02 >=20 > > If it doesn't help, is there a way to test n900 configuration in QEMU? >=20 > I doubt that QEMU n900 boots in secure mode but instead shows > the SoC as general purpose SoC. If so, you'd have to patch the > omap3_save_secure_ram_context() to attempt to save secure RAM > context in all cases. If that works then debugging with any > omap3 board like beagleboard in QEMU should work. Okay, linux-next from today still does not boot on n900. Is it something new, or was this still not fixed in -next? Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlm70xkACgkQMOfwapXb+vL0aQCgjeazCyA5h4yepRckRLzWcgNL 1gUAoIivxlb5O+Na4698mGbql2gokUAn =1a+O -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--