Bug#870185: armel/marvell kernel size
On Mon, Jul 31, 2017 at 11:43 PM, Roger Shimizu <rogershimizu@gmail.com> wrote:
> On Mon, Jul 31, 2017 at 3:05 AM, Roger Shimizu <rogershimizu@gmail.com> wrote:
>>
>> While I'm still working on this, but I find the latest kernel in
>> archive, 4.11.11-1+b1, fails to boot on my kirkwood based Linkstation.
>> I tried netconsole, but don't get any log. (netconsole outputs fine on
>> working kernels, such as 4.9 and 4.10 series.)
>> And I trace to latest working kernel is 4.10.7-1~exp1.
>>
>> 4.11-1_exp[12] FTBFS on armel, and 4.11.3-1_exp1 doesn't boot.
>>
>> I checked d-kernel and d-arm list, but didn't find similar issue.
>> Do you have any clue on this? Thanks!
>
> I think my problem is very likely the same as:
> - https://bugs.debian.org/870185
>
> And I tried Ben's recommendation to make armel kernel smaller,
> which I pushed to branch rosh/strip_armel on alioth, confirmed it worked
> well for 4.10.7-1~exp1 (by cherry-pick) on my kirkwood based Linkstation.
I find some new clue about kernel size issue for armel.
vmlinuz installed under /boot is compressed. It can be decompressed by
"scripts/extract-vmlinux" script under linux git repo. But for armel,
it need at patch I posted:
- https://patchwork.kernel.org/patch/8120831/
After I decompress the kernel images, I find the size for 4.11
increased significantly:
====
$ ~/linux/scripts/extract-vmlinux /boot/vmlinuz-4.9.0-3-marvell >
~/vmlinuz-4.9.0-3-marvell.extracted
$ ~/linux/scripts/extract-vmlinux /boot/vmlinuz-4.10.0-trunk-marvell >
~/vmlinuz-4.10.0-trunk-marvell.extracted
$ ~/linux/scripts/extract-vmlinux /boot/vmlinuz-4.11.0-0.bpo.1-marvell
> ~/vmlinuz-4.11.0-0.bpo.1-marvell.extracted
$ ls -l ~/vmlinuz-*
-rw-r--r-- 1 rosh rosh 5782024 Aug 19 12:35
vmlinuz-4.10.0-trunk-marvell.extracted
-rw-r--r-- 1 rosh rosh 8763712 Aug 19 12:36
vmlinuz-4.11.0-0.bpo.1-marvell.extracted
-rw-r--r-- 1 rosh rosh 5844072 Aug 19 12:35 vmlinuz-4.9.0-3-marvell.extracted
====
I know for bug #870185, Robert fixed his device by modify uboot
params, but I guess it's still possible to keep uboot params and only
change the boot addresses of kernel/initrd in flash-kernel db file.
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
Reply to: