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

[Tony Lindgren]

* 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

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

[Tony Lindgren]

* 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

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

[Sebastian Reichel]

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.

-- Sebastian


signature.asc
Description: PGP signature

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

[Sebastian Reichel]

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.

-- Sebastian


signature.asc
Description: PGP signature

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

[Sebastian Reichel]

[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.

-- Sebastian


signature.asc
Description: PGP signature

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

[Sebastian Reichel]

[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.

-- Sebastian


signature.asc
Description: PGP signature

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

[Tony Lindgren]

* 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?

Tony

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

[Tony Lindgren]

* 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?

Tony

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

[Sebastian Reichel]

Hi,

On Sun, Jul 16, 2017 at 10:59:42PM -0700, Tony Lindgren wrote:
> * Roman Gushchin  [170716 05:55]:
> > On Fri, Jul 14, 2017 at 07:23:43PM +0200, Sebastian Reichel wrote:
> > > On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > > > > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> > > > >  wrote:
> > > > > I just bisected another issue breaking boot on Droid 4. My
> > > > > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > > > > for oom reaper-related events). It do not see any message
> > > > > printed to UART (with earlyprintk) once that commit is part
> > > > > of my image. Kernel config is below.
> > > 
> > > > This is really interesting, because this patch adds few
> > > > tracepoints and all of them are called from the oom code, which is
> > > > hopefully not a part of the boot process.
> > > > 
> > > > Can you, please, confirm, that it can be reproduced with some
> > > > confidence? If so, can you, please, eliminate the tracepoints
> > > > calls and try to reproduce the boot failure?
> > > 
> > > I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
> > > Andrew)") after adding
> > > 
> > >  - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
> > >(another issue, that breaks Droid 4 boot)
> > >  - a git revert of 422580c3cea7
> > > 
> > > OTOH there are strange problems. Using da16dd9785f8 + above
> > > two commits also works. Using b5e16170f59b + above commits
> > > does not work and bisection ended up in the merge commit.
> > 
> > Hi, Sebastian!
> > 
> > As commit 422580c3cea7 hasn't added any code, which is executed
> > during the boot process, I could imagine only two options:
> > 1) Added code/data occasionally broke some alignment/size contraints.
> > 2) There is another instable bug, which compromised bisect results.
> > 
> > Unfortunately, I can't help you with reproducing, because I haven't
> > necessary hardware.
> > 
> > Can you, please, try some older known to be good revision with
> > the 422580c3cea7 patch applied?
> 
> 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.

-- Sebastian


signature.asc
Description: PGP signature

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

[Sebastian Reichel]

Hi,

On Sun, Jul 16, 2017 at 10:59:42PM -0700, Tony Lindgren wrote:
> * Roman Gushchin  [170716 05:55]:
> > On Fri, Jul 14, 2017 at 07:23:43PM +0200, Sebastian Reichel wrote:
> > > On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > > > > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> > > > >  wrote:
> > > > > I just bisected another issue breaking boot on Droid 4. My
> > > > > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > > > > for oom reaper-related events). It do not see any message
> > > > > printed to UART (with earlyprintk) once that commit is part
> > > > > of my image. Kernel config is below.
> > > 
> > > > This is really interesting, because this patch adds few
> > > > tracepoints and all of them are called from the oom code, which is
> > > > hopefully not a part of the boot process.
> > > > 
> > > > Can you, please, confirm, that it can be reproduced with some
> > > > confidence? If so, can you, please, eliminate the tracepoints
> > > > calls and try to reproduce the boot failure?
> > > 
> > > I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
> > > Andrew)") after adding
> > > 
> > >  - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
> > >(another issue, that breaks Droid 4 boot)
> > >  - a git revert of 422580c3cea7
> > > 
> > > OTOH there are strange problems. Using da16dd9785f8 + above
> > > two commits also works. Using b5e16170f59b + above commits
> > > does not work and bisection ended up in the merge commit.
> > 
> > Hi, Sebastian!
> > 
> > As commit 422580c3cea7 hasn't added any code, which is executed
> > during the boot process, I could imagine only two options:
> > 1) Added code/data occasionally broke some alignment/size contraints.
> > 2) There is another instable bug, which compromised bisect results.
> > 
> > Unfortunately, I can't help you with reproducing, because I haven't
> > necessary hardware.
> > 
> > Can you, please, try some older known to be good revision with
> > the 422580c3cea7 patch applied?
> 
> 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.

-- Sebastian


signature.asc
Description: PGP signature

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

[Tony Lindgren]

* Roman Gushchin  [170716 05:55]:
> On Fri, Jul 14, 2017 at 07:23:43PM +0200, Sebastian Reichel wrote:
> > Hi,
> > 
> > On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > > > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> > > >  wrote:
> > > > I just bisected another issue breaking boot on Droid 4. My
> > > > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > > > for oom reaper-related events). It do not see any message
> > > > printed to UART (with earlyprintk) once that commit is part
> > > > of my image. Kernel config is below.
> > 
> > > This is really interesting, because this patch adds few
> > > tracepoints and all of them are called from the oom code, which is
> > > hopefully not a part of the boot process.
> > > 
> > > Can you, please, confirm, that it can be reproduced with some
> > > confidence? If so, can you, please, eliminate the tracepoints
> > > calls and try to reproduce the boot failure?
> > 
> > I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
> > Andrew)") after adding
> > 
> >  - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
> >(another issue, that breaks Droid 4 boot)
> >  - a git revert of 422580c3cea7
> > 
> > OTOH there are strange problems. Using da16dd9785f8 + above
> > two commits also works. Using b5e16170f59b + above commits
> > does not work and bisection ended up in the merge commit.
> 
> Hi, Sebastian!
> 
> As commit 422580c3cea7 hasn't added any code, which is executed
> during the boot process, I could imagine only two options:
> 1) Added code/data occasionally broke some alignment/size contraints.
> 2) There is another instable bug, which compromised bisect results.
> 
> Unfortunately, I can't help you with reproducing, because I haven't
> necessary hardware.
> 
> Can you, please, try some older known to be good revision with
> the 422580c3cea7 patch applied?

Sebastian, for me droid 4 boots just fine with v4.13-rc1 +
19d39a3810e if that helps. So that's with commit 422580c3cea7.

Regards,

Tony

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

[Tony Lindgren]

* Roman Gushchin  [170716 05:55]:
> On Fri, Jul 14, 2017 at 07:23:43PM +0200, Sebastian Reichel wrote:
> > Hi,
> > 
> > On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > > > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> > > >  wrote:
> > > > I just bisected another issue breaking boot on Droid 4. My
> > > > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > > > for oom reaper-related events). It do not see any message
> > > > printed to UART (with earlyprintk) once that commit is part
> > > > of my image. Kernel config is below.
> > 
> > > This is really interesting, because this patch adds few
> > > tracepoints and all of them are called from the oom code, which is
> > > hopefully not a part of the boot process.
> > > 
> > > Can you, please, confirm, that it can be reproduced with some
> > > confidence? If so, can you, please, eliminate the tracepoints
> > > calls and try to reproduce the boot failure?
> > 
> > I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
> > Andrew)") after adding
> > 
> >  - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
> >(another issue, that breaks Droid 4 boot)
> >  - a git revert of 422580c3cea7
> > 
> > OTOH there are strange problems. Using da16dd9785f8 + above
> > two commits also works. Using b5e16170f59b + above commits
> > does not work and bisection ended up in the merge commit.
> 
> Hi, Sebastian!
> 
> As commit 422580c3cea7 hasn't added any code, which is executed
> during the boot process, I could imagine only two options:
> 1) Added code/data occasionally broke some alignment/size contraints.
> 2) There is another instable bug, which compromised bisect results.
> 
> Unfortunately, I can't help you with reproducing, because I haven't
> necessary hardware.
> 
> Can you, please, try some older known to be good revision with
> the 422580c3cea7 patch applied?

Sebastian, for me droid 4 boots just fine with v4.13-rc1 +
19d39a3810e if that helps. So that's with commit 422580c3cea7.

Regards,

Tony

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

[Roman Gushchin]

On Fri, Jul 14, 2017 at 07:23:43PM +0200, Sebastian Reichel wrote:
> Hi,
> 
> On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> > >  wrote:
> > > I just bisected another issue breaking boot on Droid 4. My
> > > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > > for oom reaper-related events). It do not see any message
> > > printed to UART (with earlyprintk) once that commit is part
> > > of my image. Kernel config is below.
> 
> > This is really interesting, because this patch adds few
> > tracepoints and all of them are called from the oom code, which is
> > hopefully not a part of the boot process.
> > 
> > Can you, please, confirm, that it can be reproduced with some
> > confidence? If so, can you, please, eliminate the tracepoints
> > calls and try to reproduce the boot failure?
> 
> I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
> Andrew)") after adding
> 
>  - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
>(another issue, that breaks Droid 4 boot)
>  - a git revert of 422580c3cea7
> 
> OTOH there are strange problems. Using da16dd9785f8 + above
> two commits also works. Using b5e16170f59b + above commits
> does not work and bisection ended up in the merge commit.

Hi, Sebastian!

As commit 422580c3cea7 hasn't added any code, which is executed
during the boot process, I could imagine only two options:
1) Added code/data occasionally broke some alignment/size contraints.
2) There is another instable bug, which compromised bisect results.

Unfortunately, I can't help you with reproducing, because I haven't
necessary hardware.

Can you, please, try some older known to be good revision with
the 422580c3cea7 patch applied?

Roman

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

[Roman Gushchin]

On Fri, Jul 14, 2017 at 07:23:43PM +0200, Sebastian Reichel wrote:
> Hi,
> 
> On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> > >  wrote:
> > > I just bisected another issue breaking boot on Droid 4. My
> > > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > > for oom reaper-related events). It do not see any message
> > > printed to UART (with earlyprintk) once that commit is part
> > > of my image. Kernel config is below.
> 
> > This is really interesting, because this patch adds few
> > tracepoints and all of them are called from the oom code, which is
> > hopefully not a part of the boot process.
> > 
> > Can you, please, confirm, that it can be reproduced with some
> > confidence? If so, can you, please, eliminate the tracepoints
> > calls and try to reproduce the boot failure?
> 
> I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
> Andrew)") after adding
> 
>  - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
>(another issue, that breaks Droid 4 boot)
>  - a git revert of 422580c3cea7
> 
> OTOH there are strange problems. Using da16dd9785f8 + above
> two commits also works. Using b5e16170f59b + above commits
> does not work and bisection ended up in the merge commit.

Hi, Sebastian!

As commit 422580c3cea7 hasn't added any code, which is executed
during the boot process, I could imagine only two options:
1) Added code/data occasionally broke some alignment/size contraints.
2) There is another instable bug, which compromised bisect results.

Unfortunately, I can't help you with reproducing, because I haven't
necessary hardware.

Can you, please, try some older known to be good revision with
the 422580c3cea7 patch applied?

Roman

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

[Sebastian Reichel]

Hi,

On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> >  wrote:
> > I just bisected another issue breaking boot on Droid 4. My
> > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > for oom reaper-related events). It do not see any message
> > printed to UART (with earlyprintk) once that commit is part
> > of my image. Kernel config is below.

> This is really interesting, because this patch adds few
> tracepoints and all of them are called from the oom code, which is
> hopefully not a part of the boot process.
> 
> Can you, please, confirm, that it can be reproduced with some
> confidence? If so, can you, please, eliminate the tracepoints
> calls and try to reproduce the boot failure?

I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
Andrew)") after adding

 - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
   (another issue, that breaks Droid 4 boot)
 - a git revert of 422580c3cea7

OTOH there are strange problems. Using da16dd9785f8 + above
two commits also works. Using b5e16170f59b + above commits
does not work and bisection ended up in the merge commit.

-- Sebastian


signature.asc
Description: PGP signature

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

[Sebastian Reichel]

Hi,

On Fri, Jul 14, 2017 at 02:12:21PM +, Roman Gushchin wrote:
> > On 14 Jul 2017, at 14:43, Sebastian Reichel 
> >  wrote:
> > I just bisected another issue breaking boot on Droid 4. My
> > bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> > for oom reaper-related events). It do not see any message
> > printed to UART (with earlyprintk) once that commit is part
> > of my image. Kernel config is below.

> This is really interesting, because this patch adds few
> tracepoints and all of them are called from the oom code, which is
> hopefully not a part of the boot process.
> 
> Can you, please, confirm, that it can be reproduced with some
> confidence? If so, can you, please, eliminate the tracepoints
> calls and try to reproduce the boot failure?

I can boot 9967468c0a10 ("Merge branch 'akpm' (patches from
Andrew)") after adding

 - http://git.kernel.org/tip/19d39a3810e7032f311ef83effdac40339b9d022
   (another issue, that breaks Droid 4 boot)
 - a git revert of 422580c3cea7

OTOH there are strange problems. Using da16dd9785f8 + above
two commits also works. Using b5e16170f59b + above commits
does not work and bisection ended up in the merge commit.

-- Sebastian


signature.asc
Description: PGP signature

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

[Roman Gushchin]

Hi Sebastian!

This is really interesting, because this patch adds few tracepoints and all of 
them are called from the oom code, which is hopefully not a part of the boot 
process.

Can you, please, confirm, that it can be reproduced with some confidence? If 
so, can you, please, eliminate the tracepoints calls and try to reproduce the 
boot failure?

Thanks!

Roman

> On 14 Jul 2017, at 14:43, Sebastian Reichel 
>  wrote:
> 
> Hi,
> 
> I just bisected another issue breaking boot on Droid 4. My
> bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> for oom reaper-related events). It do not see any message
> printed to UART (with earlyprintk) once that commit is part
> of my image. Kernel config is below.
> 
> -- Sebastian
> 
> # Automatically generated file; DO NOT EDIT.
> # Linux/arm 4.12.0 Kernel Configuration
> #
> CONFIG_ARM=y
> CONFIG_ARM_HAS_SG_CHAIN=y
> CONFIG_NEED_SG_DMA_LENGTH=y
> CONFIG_ARM_DMA_USE_IOMMU=y
> CONFIG_ARM_DMA_IOMMU_ALIGNMENT=8
> CONFIG_MIGHT_HAVE_PCI=y
> CONFIG_SYS_SUPPORTS_APM_EMULATION=y
> CONFIG_HAVE_PROC_CPU=y
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_LOCKDEP_SUPPORT=y
> CONFIG_TRACE_IRQFLAGS_SUPPORT=y
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_ARCH_HAS_BANDGAP=y
> CONFIG_FIX_EARLYCON_MEM=y
> CONFIG_GENERIC_HWEIGHT=y
> CONFIG_GENERIC_CALIBRATE_DELAY=y
> CONFIG_NEED_DMA_MAP_STATE=y
> CONFIG_ARCH_SUPPORTS_UPROBES=y
> CONFIG_VECTORS_BASE=0x
> CONFIG_ARM_PATCH_PHYS_VIRT=y
> CONFIG_GENERIC_BUG=y
> CONFIG_PGTABLE_LEVELS=2
> CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
> CONFIG_IRQ_WORK=y
> CONFIG_BUILDTIME_EXTABLE_SORT=y
> 
> #
> # General setup
> #
> CONFIG_INIT_ENV_ARG_LIMIT=32
> CONFIG_CROSS_COMPILE=""
> # CONFIG_COMPILE_TEST is not set
> CONFIG_LOCALVERSION=""
> CONFIG_LOCALVERSION_AUTO=y
> CONFIG_HAVE_KERNEL_GZIP=y
> CONFIG_HAVE_KERNEL_LZMA=y
> CONFIG_HAVE_KERNEL_XZ=y
> CONFIG_HAVE_KERNEL_LZO=y
> CONFIG_HAVE_KERNEL_LZ4=y
> CONFIG_KERNEL_GZIP=y
> # CONFIG_KERNEL_LZMA is not set
> # CONFIG_KERNEL_XZ is not set
> # CONFIG_KERNEL_LZO is not set
> # CONFIG_KERNEL_LZ4 is not set
> CONFIG_DEFAULT_HOSTNAME="(none)"
> CONFIG_SWAP=y
> CONFIG_SYSVIPC=y
> CONFIG_SYSVIPC_SYSCTL=y
> CONFIG_POSIX_MQUEUE=y
> CONFIG_POSIX_MQUEUE_SYSCTL=y
> CONFIG_CROSS_MEMORY_ATTACH=y
> CONFIG_FHANDLE=y
> CONFIG_USELIB=y
> CONFIG_AUDIT=y
> CONFIG_HAVE_ARCH_AUDITSYSCALL=y
> CONFIG_AUDITSYSCALL=y
> CONFIG_AUDIT_WATCH=y
> CONFIG_AUDIT_TREE=y
> 
> #
> # IRQ subsystem
> #
> CONFIG_GENERIC_IRQ_PROBE=y
> CONFIG_GENERIC_IRQ_SHOW=y
> CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
> CONFIG_HARDIRQS_SW_RESEND=y
> CONFIG_GENERIC_IRQ_CHIP=y
> CONFIG_IRQ_DOMAIN=y
> CONFIG_IRQ_DOMAIN_HIERARCHY=y
> CONFIG_HANDLE_DOMAIN_IRQ=y
> # CONFIG_IRQ_DOMAIN_DEBUG is not set
> CONFIG_IRQ_FORCED_THREADING=y
> CONFIG_SPARSE_IRQ=y
> CONFIG_GENERIC_IRQ_DEBUGFS=y
> CONFIG_ARCH_CLOCKSOURCE_DATA=y
> CONFIG_GENERIC_TIME_VSYSCALL=y
> CONFIG_GENERIC_CLOCKEVENTS=y
> CONFIG_ARCH_HAS_TICK_BROADCAST=y
> CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
> 
> #
> # Timers subsystem
> #
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ_COMMON=y
> # CONFIG_HZ_PERIODIC is not set
> CONFIG_NO_HZ_IDLE=y
> # CONFIG_NO_HZ_FULL is not set
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
> 
> #
> # CPU/Task time and stats accounting
> #
> CONFIG_TICK_CPU_ACCOUNTING=y
> # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
> # CONFIG_IRQ_TIME_ACCOUNTING is not set
> CONFIG_BSD_PROCESS_ACCT=y
> # CONFIG_BSD_PROCESS_ACCT_V3 is not set
> # CONFIG_TASKSTATS is not set
> 
> #
> # RCU Subsystem
> #
> CONFIG_TREE_RCU=y
> # CONFIG_RCU_EXPERT is not set
> CONFIG_SRCU=y
> CONFIG_TREE_SRCU=y
> # CONFIG_TASKS_RCU is not set
> CONFIG_RCU_STALL_COMMON=y
> CONFIG_RCU_NEED_SEGCBLIST=y
> CONFIG_BUILD_BIN2C=y
> CONFIG_IKCONFIG=y
> CONFIG_IKCONFIG_PROC=y
> CONFIG_LOG_BUF_SHIFT=16
> CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
> CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
> CONFIG_GENERIC_SCHED_CLOCK=y
> CONFIG_CGROUPS=y
> CONFIG_PAGE_COUNTER=y
> CONFIG_MEMCG=y
> CONFIG_MEMCG_SWAP=y
> CONFIG_MEMCG_SWAP_ENABLED=y
> CONFIG_BLK_CGROUP=y
> # CONFIG_DEBUG_BLK_CGROUP is not set
> CONFIG_CGROUP_WRITEBACK=y
> CONFIG_CGROUP_SCHED=y
> CONFIG_FAIR_GROUP_SCHED=y
> CONFIG_CFS_BANDWIDTH=y
> CONFIG_RT_GROUP_SCHED=y
> # CONFIG_CGROUP_PIDS is not set
> # CONFIG_CGROUP_RDMA is not set
> CONFIG_CGROUP_FREEZER=y
> CONFIG_CPUSETS=y
> CONFIG_PROC_PID_CPUSET=y
> CONFIG_CGROUP_DEVICE=y
> CONFIG_CGROUP_CPUACCT=y
> CONFIG_CGROUP_PERF=y
> # CONFIG_CGROUP_DEBUG is not set
> # CONFIG_SOCK_CGROUP_DATA is not set
> # CONFIG_CHECKPOINT_RESTORE is not set
> CONFIG_NAMESPACES=y
> CONFIG_UTS_NS=y
> CONFIG_IPC_NS=y
> # CONFIG_USER_NS is not set
> CONFIG_PID_NS=y
> CONFIG_NET_NS=y
> # CONFIG_SCHED_AUTOGROUP is not set
> # CONFIG_SYSFS_DEPRECATED is not set
> # CONFIG_RELAY is not set
> CONFIG_BLK_DEV_INITRD=y
> CONFIG_INITRAMFS_SOURCE=""
> CONFIG_RD_GZIP=y
> CONFIG_RD_BZIP2=y
> CONFIG_RD_LZMA=y
> CONFIG_RD_XZ=y
> CONFIG_RD_LZO=y
> CONFIG_RD_LZ4=y
> CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
> # CONFIG_CC_OPTIMIZE_FOR_SIZE is not 

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

[Roman Gushchin]

Hi Sebastian!

This is really interesting, because this patch adds few tracepoints and all of 
them are called from the oom code, which is hopefully not a part of the boot 
process.

Can you, please, confirm, that it can be reproduced with some confidence? If 
so, can you, please, eliminate the tracepoints calls and try to reproduce the 
boot failure?

Thanks!

Roman

> On 14 Jul 2017, at 14:43, Sebastian Reichel 
>  wrote:
> 
> Hi,
> 
> I just bisected another issue breaking boot on Droid 4. My
> bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
> for oom reaper-related events). It do not see any message
> printed to UART (with earlyprintk) once that commit is part
> of my image. Kernel config is below.
> 
> -- Sebastian
> 
> # Automatically generated file; DO NOT EDIT.
> # Linux/arm 4.12.0 Kernel Configuration
> #
> CONFIG_ARM=y
> CONFIG_ARM_HAS_SG_CHAIN=y
> CONFIG_NEED_SG_DMA_LENGTH=y
> CONFIG_ARM_DMA_USE_IOMMU=y
> CONFIG_ARM_DMA_IOMMU_ALIGNMENT=8
> CONFIG_MIGHT_HAVE_PCI=y
> CONFIG_SYS_SUPPORTS_APM_EMULATION=y
> CONFIG_HAVE_PROC_CPU=y
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_LOCKDEP_SUPPORT=y
> CONFIG_TRACE_IRQFLAGS_SUPPORT=y
> CONFIG_RWSEM_XCHGADD_ALGORITHM=y
> CONFIG_ARCH_HAS_BANDGAP=y
> CONFIG_FIX_EARLYCON_MEM=y
> CONFIG_GENERIC_HWEIGHT=y
> CONFIG_GENERIC_CALIBRATE_DELAY=y
> CONFIG_NEED_DMA_MAP_STATE=y
> CONFIG_ARCH_SUPPORTS_UPROBES=y
> CONFIG_VECTORS_BASE=0x
> CONFIG_ARM_PATCH_PHYS_VIRT=y
> CONFIG_GENERIC_BUG=y
> CONFIG_PGTABLE_LEVELS=2
> CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
> CONFIG_IRQ_WORK=y
> CONFIG_BUILDTIME_EXTABLE_SORT=y
> 
> #
> # General setup
> #
> CONFIG_INIT_ENV_ARG_LIMIT=32
> CONFIG_CROSS_COMPILE=""
> # CONFIG_COMPILE_TEST is not set
> CONFIG_LOCALVERSION=""
> CONFIG_LOCALVERSION_AUTO=y
> CONFIG_HAVE_KERNEL_GZIP=y
> CONFIG_HAVE_KERNEL_LZMA=y
> CONFIG_HAVE_KERNEL_XZ=y
> CONFIG_HAVE_KERNEL_LZO=y
> CONFIG_HAVE_KERNEL_LZ4=y
> CONFIG_KERNEL_GZIP=y
> # CONFIG_KERNEL_LZMA is not set
> # CONFIG_KERNEL_XZ is not set
> # CONFIG_KERNEL_LZO is not set
> # CONFIG_KERNEL_LZ4 is not set
> CONFIG_DEFAULT_HOSTNAME="(none)"
> CONFIG_SWAP=y
> CONFIG_SYSVIPC=y
> CONFIG_SYSVIPC_SYSCTL=y
> CONFIG_POSIX_MQUEUE=y
> CONFIG_POSIX_MQUEUE_SYSCTL=y
> CONFIG_CROSS_MEMORY_ATTACH=y
> CONFIG_FHANDLE=y
> CONFIG_USELIB=y
> CONFIG_AUDIT=y
> CONFIG_HAVE_ARCH_AUDITSYSCALL=y
> CONFIG_AUDITSYSCALL=y
> CONFIG_AUDIT_WATCH=y
> CONFIG_AUDIT_TREE=y
> 
> #
> # IRQ subsystem
> #
> CONFIG_GENERIC_IRQ_PROBE=y
> CONFIG_GENERIC_IRQ_SHOW=y
> CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
> CONFIG_HARDIRQS_SW_RESEND=y
> CONFIG_GENERIC_IRQ_CHIP=y
> CONFIG_IRQ_DOMAIN=y
> CONFIG_IRQ_DOMAIN_HIERARCHY=y
> CONFIG_HANDLE_DOMAIN_IRQ=y
> # CONFIG_IRQ_DOMAIN_DEBUG is not set
> CONFIG_IRQ_FORCED_THREADING=y
> CONFIG_SPARSE_IRQ=y
> CONFIG_GENERIC_IRQ_DEBUGFS=y
> CONFIG_ARCH_CLOCKSOURCE_DATA=y
> CONFIG_GENERIC_TIME_VSYSCALL=y
> CONFIG_GENERIC_CLOCKEVENTS=y
> CONFIG_ARCH_HAS_TICK_BROADCAST=y
> CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
> 
> #
> # Timers subsystem
> #
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ_COMMON=y
> # CONFIG_HZ_PERIODIC is not set
> CONFIG_NO_HZ_IDLE=y
> # CONFIG_NO_HZ_FULL is not set
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
> 
> #
> # CPU/Task time and stats accounting
> #
> CONFIG_TICK_CPU_ACCOUNTING=y
> # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
> # CONFIG_IRQ_TIME_ACCOUNTING is not set
> CONFIG_BSD_PROCESS_ACCT=y
> # CONFIG_BSD_PROCESS_ACCT_V3 is not set
> # CONFIG_TASKSTATS is not set
> 
> #
> # RCU Subsystem
> #
> CONFIG_TREE_RCU=y
> # CONFIG_RCU_EXPERT is not set
> CONFIG_SRCU=y
> CONFIG_TREE_SRCU=y
> # CONFIG_TASKS_RCU is not set
> CONFIG_RCU_STALL_COMMON=y
> CONFIG_RCU_NEED_SEGCBLIST=y
> CONFIG_BUILD_BIN2C=y
> CONFIG_IKCONFIG=y
> CONFIG_IKCONFIG_PROC=y
> CONFIG_LOG_BUF_SHIFT=16
> CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
> CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
> CONFIG_GENERIC_SCHED_CLOCK=y
> CONFIG_CGROUPS=y
> CONFIG_PAGE_COUNTER=y
> CONFIG_MEMCG=y
> CONFIG_MEMCG_SWAP=y
> CONFIG_MEMCG_SWAP_ENABLED=y
> CONFIG_BLK_CGROUP=y
> # CONFIG_DEBUG_BLK_CGROUP is not set
> CONFIG_CGROUP_WRITEBACK=y
> CONFIG_CGROUP_SCHED=y
> CONFIG_FAIR_GROUP_SCHED=y
> CONFIG_CFS_BANDWIDTH=y
> CONFIG_RT_GROUP_SCHED=y
> # CONFIG_CGROUP_PIDS is not set
> # CONFIG_CGROUP_RDMA is not set
> CONFIG_CGROUP_FREEZER=y
> CONFIG_CPUSETS=y
> CONFIG_PROC_PID_CPUSET=y
> CONFIG_CGROUP_DEVICE=y
> CONFIG_CGROUP_CPUACCT=y
> CONFIG_CGROUP_PERF=y
> # CONFIG_CGROUP_DEBUG is not set
> # CONFIG_SOCK_CGROUP_DATA is not set
> # CONFIG_CHECKPOINT_RESTORE is not set
> CONFIG_NAMESPACES=y
> CONFIG_UTS_NS=y
> CONFIG_IPC_NS=y
> # CONFIG_USER_NS is not set
> CONFIG_PID_NS=y
> CONFIG_NET_NS=y
> # CONFIG_SCHED_AUTOGROUP is not set
> # CONFIG_SYSFS_DEPRECATED is not set
> # CONFIG_RELAY is not set
> CONFIG_BLK_DEV_INITRD=y
> CONFIG_INITRAMFS_SOURCE=""
> CONFIG_RD_GZIP=y
> CONFIG_RD_BZIP2=y
> CONFIG_RD_LZMA=y
> CONFIG_RD_XZ=y
> CONFIG_RD_LZO=y
> CONFIG_RD_LZ4=y
> CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
> # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
> CONFIG_SYSCTL=y
> 

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

[Sebastian Reichel]

Hi,

I just bisected another issue breaking boot on Droid 4. My
bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
for oom reaper-related events). It do not see any message
printed to UART (with earlyprintk) once that commit is part
of my image. Kernel config is below.

-- Sebastian

# Automatically generated file; DO NOT EDIT.
# Linux/arm 4.12.0 Kernel Configuration
#
CONFIG_ARM=y
CONFIG_ARM_HAS_SG_CHAIN=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_ARM_DMA_USE_IOMMU=y
CONFIG_ARM_DMA_IOMMU_ALIGNMENT=8
CONFIG_MIGHT_HAVE_PCI=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_BANDGAP=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_VECTORS_BASE=0x
CONFIG_ARM_PATCH_PHYS_VIRT=y
CONFIG_GENERIC_BUG=y
CONFIG_PGTABLE_LEVELS=2
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_HANDLE_DOMAIN_IRQ=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_DEBUGFS=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
CONFIG_GENERIC_SCHED_CLOCK=y
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_SWAP_ENABLED=y
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
CONFIG_RT_GROUP_SCHED=y
# CONFIG_CGROUP_PIDS is not set
# CONFIG_CGROUP_RDMA is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_SOCK_CGROUP_DATA is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_BPF=y
CONFIG_EXPERT=y
CONFIG_UID16=y
CONFIG_MULTIUSER=y
# CONFIG_SGETMASK_SYSCALL is not set
CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_POSIX_TIMERS=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_ABSOLUTE_PERCPU is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
# CONFIG_BPF_SYSCALL is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_USERFAULTFD=y
CONFIG_MEMBARRIER=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y
# CONFIG_PC104 is not set

#
# Kernel Performance Events And Counters
#

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

[Sebastian Reichel]

Hi,

I just bisected another issue breaking boot on Droid 4. My
bisect points to 422580c3cea7 (mm/oom_kill.c: add tracepoints
for oom reaper-related events). It do not see any message
printed to UART (with earlyprintk) once that commit is part
of my image. Kernel config is below.

-- Sebastian

# Automatically generated file; DO NOT EDIT.
# Linux/arm 4.12.0 Kernel Configuration
#
CONFIG_ARM=y
CONFIG_ARM_HAS_SG_CHAIN=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_ARM_DMA_USE_IOMMU=y
CONFIG_ARM_DMA_IOMMU_ALIGNMENT=8
CONFIG_MIGHT_HAVE_PCI=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_BANDGAP=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_VECTORS_BASE=0x
CONFIG_ARM_PATCH_PHYS_VIRT=y
CONFIG_GENERIC_BUG=y
CONFIG_PGTABLE_LEVELS=2
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_HANDLE_DOMAIN_IRQ=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_DEBUGFS=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TREE_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
CONFIG_GENERIC_SCHED_CLOCK=y
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_SWAP_ENABLED=y
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
CONFIG_RT_GROUP_SCHED=y
# CONFIG_CGROUP_PIDS is not set
# CONFIG_CGROUP_RDMA is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_SOCK_CGROUP_DATA is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_BPF=y
CONFIG_EXPERT=y
CONFIG_UID16=y
CONFIG_MULTIUSER=y
# CONFIG_SGETMASK_SYSCALL is not set
CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_POSIX_TIMERS=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_ABSOLUTE_PERCPU is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
# CONFIG_BPF_SYSCALL is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_USERFAULTFD=y
CONFIG_MEMBARRIER=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y
# CONFIG_PC104 is not set

#
# Kernel Performance Events And Counters
#