From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add tracepoints for oom reaper-related events) Date: Mon, 17 Jul 2017 23:00:49 -0700 Message-ID: <20170718060049.GM10026@atomide.com> References: <20170714134330.bsdoopceecuk5yem@earth> <20170714172343.szrjbeob5alpgzpe@earth> <20170716125354.GA20017@castle> <20170717055942.GA10026@atomide.com> <20170717095139.gv3dmh7mhyzmh7bn@earth> <20170717101927.GJ10026@atomide.com> <20170717111713.2lzgplta7mx7xfy3@earth> <20170717115128.u3caqnyiqcnuytz5@earth> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8BIT Return-path: Content-Disposition: inline In-Reply-To: <20170717115128.u3caqnyiqcnuytz5@earth> Sender: linux-kernel-owner@vger.kernel.org To: Sebastian Reichel Cc: Linux-Kernel , Linux-OMAP List-Id: linux-omap@vger.kernel.org * Sebastian Reichel [170717 04:52]: > Hi, > > On Mon, Jul 17, 2017 at 01:17:13PM +0200, Sebastian Reichel wrote: > > [dropping people from Cc] > > > > Hi, > > > > On Mon, Jul 17, 2017 at 03:19:28AM -0700, Tony Lindgren wrote: > > > * Sebastian Reichel [170717 02:52]: > > > > On Sun, Jul 16, 2017 at 10:59:42PM -0700, Tony Lindgren wrote: > > > > > Sebastian, for me droid 4 boots just fine with v4.13-rc1 + > > > > > 19d39a3810e if that helps. So that's with commit 422580c3cea7. > > > > > > > > v4.13-rc1 + 19d39a3810e was also broken for me. I just disabled > > > > some unused bits in my .config and now the kernel boots with > > > > (with 422580c3cea7 that is). Maybe I hit some maximum image size > > > > limit for Droid 4? > > > > > > > > Anyways it looks like 422580c3cea7 is not the actual problem > > > > and merely reveals some other problem. > > > > > > OK. Maybe check kexec --image-size configuration if you have > > > a huge static kernel? > > > > I still use the IMGSIZE=26214400 from your kexec wrapper for > > Droid 4, which should be 25MB. With the updated .config my > > image looks like this: > > > > $ ls -lh arch/arm/boot/*Image > > -rwxr-xr-x 1 sre sre 17M Jul 17 12:44 arch/arm/boot/Image > > -rwxr-xr-x 1 sre sre 7.2M Jul 17 12:44 arch/arm/boot/zImage > > > > Unfortunately I did not check size before I dropped the config > > options. I don't think I removed 8M of config options, but who > > knows. > > I just enabled CONFIG_DEBUG_LOCKDEP=y and CONFIG_DEBUG_ATOMIC_SLEEP=y > and it did not boot again. Sizes are much smaller than kexec's > image-size parameter (26214400 - 25MB): > > $ ls -l arch/arm/boot/Image > -rwxr-xr-x 1 sre sre 17768448 Jul 12 00:38 arch/arm/boot/Image > > Then I increased image-size parameter to 33554432 (32MB) and it > boots again. So looks like it is a size problem. I wonder what > size this is about, though. Well recent kexec-tools attempts to calculate the size automatically looking at kexec-tools commit 8d614008609f ("arm: use zImage size from header"). Maybe check what your zImage header says for end - start? Regards, Tony