From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: v3.19-rc1 regression(?) on N900 Date: Thu, 25 Dec 2014 10:11:21 +0100 Message-ID: <20141225091121.GA20355@amd> References: <549B44E2.6080202@ti.com> <201412250932.40403@pali> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:53988 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751968AbaLYJLY (ORCPT ); Thu, 25 Dec 2014 04:11:24 -0500 Content-Disposition: inline In-Reply-To: <201412250932.40403@pali> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Pali =?iso-8859-1?Q?Roh=E1r?= Cc: Nishanth Menon , linux-omap , sre@debian.org, sre@ring0.de, aaro.koskinen@iki.fi, tony@atomide.com, ivo.g.dimitrov.75@gmail.com, linux-arm-kernel , kernel list On Thu 2014-12-25 09:32:40, Pali Roh=E1r wrote: > On Wednesday 24 December 2014 23:57:38 Nishanth Menon wrote: > > based on automated testing with u-boot as a chained > > bootloader.. > >=20 > > v3.18: boots fine: > > https://github.com/nmenon/kernel-test-logs/blob/v3.18/omap2plu > > s_defconfig/n900.txt > >=20 > > v3.19-rc1: hung > > https://github.com/nmenon/kernel-test-logs/blob/v3.19-rc1/omap > > 2plus_defconfig/n900.txt > >=20 > > in the interim, my farm had a bit of breakdown around the time > > of n900 breakdown.. > >=20 > > as per my last functional linux-next logs: > > https://github.com/nmenon/kernel-test-logs/blob/next-20141204/ > > omap2plus_defconfig/n900.txt -> hung. > > https://github.com/nmenon/kernel-test-logs/blob/next-20141112/ > > omap2plus_defconfig/n900.txt -> working. > >=20 > > DEBUG_LL, CONFIG_DEBUG_OMAP3UART3=3Dy and early_printk did not > > yield information either Early hang, independend on config. That's "dtb too big". Delete something, and it should work again. Plus you'll note video regression. # > I test-merged 3315764efceaccfb02c7d4c99ef8eed6716cd861, and boom, # > video is gone. # # I reverted # # > 4b4123f0c7b02f7cf1a3189f967f079197578c3a..9051909e451a0368c95ccf745= 62adb53fd2719f8 # in 3.19, and voila, video is back. > CCing other people. >=20 > I see same problem in qemu with 3.19-rc1 kernel when doing DT=20 > boot. In qemu I'm using direct booting from OneNAND (X-Loader -->=20 > NOLO --> kernel) without U-Boot. After NOLO load & boot kernel I=20 > do not see any other output from serial console. Also on qemu=20 > screen there is no new output (just NOKIA logo from bootloader). >=20 > I do not have this problem when doing legacy/board code boot with=20 > 3.19-rc1 kernel, so this problem is related to DT. >=20 > Kernel 3.18-rc1 worked fine for both DT and legacy boot. >=20 > Can somebody look what broke DT booting? It was too big dtb, at least for me. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses= /blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html