[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170717101927.GJ10026@atomide.com>
Date: Mon, 17 Jul 2017 03:19:28 -0700
From: Tony Lindgren <tony@...mide.com>
To: Sebastian Reichel <sebastian.reichel@...labora.co.uk>
Cc: Roman Gushchin <guro@...com>, Michal Hocko <mhocko@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux-Kernel <linux-kernel@...r.kernel.org>,
Linux-OMAP <linux-omap@...r.kernel.org>
Subject: Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add
tracepoints for oom reaper-related events)
* Sebastian Reichel <sebastian.reichel@...labora.co.uk> [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?
Tony
Powered by blists - more mailing lists