On Sun, 2017-08-20 at 02:35 +0900, Roger Shimizu wrote: > On Sun, Aug 20, 2017 at 12:55 AM, Ian Campbell <ijc@debian.org> > wrote: > > On Sat, 2017-08-19 at 12:57 +0900, Roger Shimizu wrote: > > > 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. > > > > In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870185#35 I > > concluded it wasn't, perhaps I'm wrong though. > > You may read my previous research: > - https://bugs.debian.org/809476#49 > > > Can someone confirm whether the issue is that the u-boot load > > addresses > > for kernel and initrd are conflicting or if it is the kernel's > > target/decompression address and u-boot's initrd address which are > > conflicting? The symptoms seem to suggest the kernel is being > > decompressed over the initrd. > > The real problem is kernel size (after decompression) increased from > 5MB to 8MB. (detail is in my previous post) > This looks like a bug, since usually kernel size grows gradually, not > in +3MB way this time. Some things to check: - If you build 4.10 with the config used for 4.11 (whichever is the first larger one), is the size 5 MB or 8 MB? - If not, try bisecting the upstream source to find a jump in size. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou
Attachment:
signature.asc
Description: This is a digitally signed message part