On Sun, Aug 27, 2017 at 1:31 AM, Roger Shimizu wrote:
> On Sun, Aug 27, 2017 at 1:27 AM, Roger Shimizu wrote:
>> On Tue, Aug 22, 2017 at 2:55 AM, Ben Hutchings wrote:
>>> For the size check, you're mostly duplicating the existing check_size()
>>> function. It would be preferable to have a singl
On Mon, 2017-08-28 at 00:34 +0900, Roger Shimizu wrote:
> On Sun, Aug 27, 2017 at 1:31 AM, Roger Shimizu wrote:
> > On Sun, Aug 27, 2017 at 1:27 AM, Roger Shimizu
> > wrote:
> > > On Tue, Aug 22, 2017 at 2:55 AM, Ben Hutchings
> > > wrote:
> > > > For the size check, you're mostly duplicating
On Sun, Aug 27, 2017 at 1:27 AM, Roger Shimizu wrote:
> On Tue, Aug 22, 2017 at 2:55 AM, Ben Hutchings wrote:
>> For the size check, you're mostly duplicating the existing check_size()
>> function. It would be preferable to have a single function with some
>> extra parameters so that it can do b
On Tue, Aug 22, 2017 at 2:55 AM, Ben Hutchings wrote:
> On Tue, 2017-08-22 at 01:22 +0900, Roger Shimizu wrote:
>
> Oh I see, that adds section (1 MiB) alignment in several places.
> Surprisingly, the padding isn't completely zero-filled, so it inflates
> the compressed image size too.
Good to kn
On Tue, 2017-08-22 at 01:22 +0900, Roger Shimizu wrote:
> Control: tag -1 +pending
>
> On Mon, Aug 21, 2017 at 9:28 AM, Roger Shimizu wrote:
> > On Mon, Aug 21, 2017 at 12:43 AM, Ben Hutchings
> > wrote:
> > >
> > > OK, then try using 4.11.6 source and bisecting the Debian config
> > > changes
Control: tag -1 +pending
On Mon, Aug 21, 2017 at 9:28 AM, Roger Shimizu wrote:
> On Mon, Aug 21, 2017 at 12:43 AM, Ben Hutchings wrote:
>>
>> OK, then try using 4.11.6 source and bisecting the Debian config
>> changes.
>
> Result:
> 0905519af414d339f615d7aac974f9a9163cdbd3 is the first bad commi
On Mon, Aug 21, 2017 at 12:43 AM, Ben Hutchings wrote:
>
> OK, then try using 4.11.6 source and bisecting the Debian config
> changes.
Result:
0905519af414d339f615d7aac974f9a9163cdbd3 is the first bad commit
Here's the detailed log.
$ git bisect log
git bisect start
# good: [327c328b5435d93c2d3
On Sun, 2017-08-20 at 21:16 +0900, Roger Shimizu wrote:
> On Sun, Aug 20, 2017 at 6:54 AM, Ben Hutchings
> wrote:
> > On Sun, 2017-08-20 at 02:35 +0900, Roger Shimizu wrote:
> > >
> > > The real problem is kernel size (after decompression) increased
> > > from
> > > 5MB to 8MB. (detail is in my p
On Sun, Aug 20, 2017 at 6:54 AM, Ben Hutchings wrote:
> On Sun, 2017-08-20 at 02:35 +0900, Roger Shimizu wrote:
>>
>> 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 gradua
On Sun, 2017-08-20 at 02:35 +0900, Roger Shimizu wrote:
> On Sun, Aug 20, 2017 at 12:55 AM, Ian Campbell
> 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
On Sun, Aug 20, 2017 at 12:55 AM, Ian Campbell 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
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
On Mon, Jul 31, 2017 at 11:43 PM, Roger Shimizu wrote:
> On Mon, Jul 31, 2017 at 3:05 AM, Roger Shimizu 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
13 matches
Mail list logo
