Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add tracepoints for oom reaper-related events)

From	Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Newsgroups	linux.kernel
Subject	Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add tracepoints for oom reaper-related events)
Date	2017-07-17 13:20 +0200
Message-ID	<u4cee-4iB-25@gated-at.bofh.it> (permalink)
References	(2 earlier) <u3czE-6A0-7@gated-at.bofh.it> <u47oe-1fK-13@gated-at.bofh.it> <u47oe-1fK-11@gated-at.bofh.it> <u4aYO-3lP-13@gated-at.bofh.it> <u4bia-3Jo-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

[dropping people from Cc]

Hi,

On Mon, Jul 17, 2017 at 03:19:28AM -0700, Tony Lindgren wrote:
> * 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?

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.

-- Sebastian

Thread

Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add  tracepoints for oom reaper-related events) Sebastian Reichel <sebastian.reichel@collabora.co.uk> - 2017-07-14 19:30 +0200
  Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add  tracepoints for oom reaper-related events) Tony Lindgren <tony@atomide.com> - 2017-07-17 08:10 +0200
    Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add  tracepoints for oom reaper-related events) Sebastian Reichel <sebastian.reichel@collabora.co.uk> - 2017-07-17 12:00 +0200
      Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add  tracepoints for oom reaper-related events) Tony Lindgren <tony@atomide.com> - 2017-07-17 12:20 +0200
        Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add  tracepoints for oom reaper-related events) Sebastian Reichel <sebastian.reichel@collabora.co.uk> - 2017-07-17 13:20 +0200
          Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add  tracepoints for oom reaper-related events) Sebastian Reichel <sebastian.reichel@collabora.co.uk> - 2017-07-17 14:00 +0200
            Re: Droid 4 boot failure due to 422580c3cea7 (mm/oom_kill.c: add  tracepoints for oom reaper-related events) Tony Lindgren <tony@atomide.com> - 2017-07-18 08:10 +0200

csiph-web