From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: Roman Gushchin <guro@fb.com>, Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>
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 03:19:28 -0700 [thread overview]
Message-ID: <20170717101927.GJ10026@atomide.com> (raw)
In-Reply-To: <20170717095139.gv3dmh7mhyzmh7bn@earth>
* Sebastian Reichel <sebastian.reichel@collabora.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
next prev parent reply other threads:[~2017-07-17 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 13:43 Sebastian Reichel
2017-07-14 14:12 ` Roman Gushchin
2017-07-14 17:23 ` Sebastian Reichel
2017-07-16 12:53 ` Roman Gushchin
2017-07-17 5:59 ` Tony Lindgren
2017-07-17 9:51 ` Sebastian Reichel
2017-07-17 10:19 ` Tony Lindgren [this message]
2017-07-17 11:17 ` Sebastian Reichel
2017-07-17 11:51 ` Sebastian Reichel
2017-07-18 6:00 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170717101927.GJ10026@atomide.com \
--to=tony@atomide.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=sebastian.reichel@collabora.co.uk \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome