Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II

From	Ben Hutchings <ben@decadent.org.uk>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II
Date	2017-08-12 23:10 +0200
Message-ID	<udLPs-698-13@gated-at.bofh.it> (permalink)
References	<u92xA-4C8-19@gated-at.bofh.it> <u974d-7xK-3@gated-at.bofh.it> <u9lAe-8rv-7@gated-at.bofh.it> <u92xA-4C8-19@gated-at.bofh.it> <u9lAe-8rv-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

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

On Mon, 2017-07-31 at 18:10 +0200, Robert Schlabbach wrote:
> Ok, I figured it out. I noticed that the 4.11 kernel has a more
> "generous" memory layout than the 4.9 one:
> 
> kernel 4.9:
> 
> [    0.000000] Memory: 504492K/524288K available (3777K kernel code, 371K rwdata, 1128K rodata, 296K init, 247K bss, 19796K reserved, 0K cma-reserved, 0K highmem)
> 
> kernel 4.11:
> 
> [    0.000000] Memory: 502648K/524288K available (4096K kernel code, 398K rwdata, 1132K rodata, 1024K init, 248K bss, 21640K reserved, 0K cma-reserved, 0K highmem)
> 
> So I suspected that the 4.11 kernel might be overwriting/corrupting
> the initrd.img provided in memory before it gets to unpack it, and
> changed the memory location from 0xa00000 to 0xc00000:
[...]
> Voila! It's finally booting!
> 
> So, was the 4.11 kernel compiled/linked with a wrong alignment
> padding setting? Or should the bootloader environment be changed to
> permanently use the higher address for passing initrd.img to the
> kernel?

Should this be assigned to flash-kernel?

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.

Thread

Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II "Robert Schlabbach" <Robert.Schlabbach@gmx.net> - 2017-07-30 22:00 +0200
  Bug#870185: Acknowledgement (FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II) "Robert Schlabbach" <Robert.Schlabbach@gmx.net> - 2017-07-31 02:50 +0200
  Bug#870185: Acknowledgement (FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II) "Robert Schlabbach" <Robert.Schlabbach@gmx.net> - 2017-07-31 12:10 +0200
  Bug#870185: Acknowledgement (FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II) "Robert Schlabbach" <Robert.Schlabbach@gmx.net> - 2017-07-31 17:50 +0200
  Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II "Robert Schlabbach" <Robert.Schlabbach@gmx.net> - 2017-07-31 18:20 +0200
    Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II Ben Hutchings <ben@decadent.org.uk> - 2017-08-12 23:10 +0200
      Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II Ian Campbell <ijc@debian.org> - 2017-08-13 11:00 +0200
        Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II "Robert Schlabbach" <Robert.Schlabbach@gmx.net> - 2017-08-13 12:10 +0200
          Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II Ian Campbell <ijc@debian.org> - 2017-08-13 12:10 +0200
  Processed: Re: Bug#870185: armel/marvell kernel size owner@bugs.debian.org (Debian Bug Tracking System) - 2017-08-21 18:30 +0200

csiph-web