Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1689753

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

Show all headers | View raw

* Sebastian Reichel <sebastian.reichel@collabora.co.uk> [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 <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.
> 
> 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

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

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