Failed image builds

[phedny]

I have made several pieces of firmware, some of them working, some not. I noticed that all 'problematic' firmwares have something like this in the build output: 'warning: increasing offset 939566 to 939568'. Could this be the cause and if so, how can I fix it?

Example output context:


( . /root/broadcom/src/linux/linux/.config ; \
if [ "${CONFIG_EMBEDDED_RAMDISK}" = "y" ] ; then \
cp /root/broadcom/src/gateway/mipsel-uclibc/target.cramfs /root/broadcom/src/linux/linux/arch/mips/ramdisk/${CONFIG_EMBEDDED_RAMDISK_IMAGE} ; \
make -C /root/broadcom/src/linux/linux zImage ; \
else \
cp /root/broadcom/src/linux/linux/arch/mips/brcm-boards/bcm947xx/compressed/vmlinuz /root/broadcom/src/gateway/mipsel-uclibc/ ; \
addver /root/broadcom/src/gateway/mipsel-uclibc/target.cramfs 1.8 1.7 WL500g \
"0.02" "2.99" "" "" "" "" "" "" /root/broadcom/src/gateway/mipsel-uclibc/vmlinuz; \
trx -o /root/broadcom/src/gateway/mipsel-uclibc/WL500g-1.8.1.7-3.trx /root/broadcom/src/gateway/mipsel-uclibc/vmlinuz /root/broadcom/src/gateway/mipsel-uclibc/target.cramfs ; \
fi )
Append Version Information to file ...
Kernel Version : 1.8
File system Version : 1.7
Product ID : WL500g $
Hardware compatible list:
1: 0.2
2: 2.99
3: 0.0
4: 0.0
5: 0.0
6: 0.0
7: 0.0
8: 0.0
K: 939538
Kernel size : /root/broadcom/src/gateway/mipsel-uclibc/vmlinuz e5630
File Length: 2359296
warning: increasing offset 939566 to 939568
cp /root/broadcom/src/linux/linux/arch/mips/brcm-boards/bcm947xx/compressed/zImage /root/broadcom/src/gateway/mipsel-uclibc/
dd conv=sync bs=64k < /root/broadcom/src/gateway/mipsel-uclibc/zImage > /root/broadcom/src/gateway/mipsel-uclibc/linux.bin
13+1 records in
14+0 records out
cat /root/broadcom/src/gateway/mipsel-uclibc/target.cramfs >> /root/broadcom/src/gateway/mipsel-uclibc/linux.bin

[Oleg]

No, this is not a problem. Seems you've exceeded maximum image size - 0x3a0000.

[phedny]

Does it mean the image size is truncated or so? If so, which means (binary) data might be lost, could it result in programs giving a SEGFAULT?

[phedny]

Just made a new image, striping out some software to cut down on the size and the resizing error disappeared.

But the SEGFAULT is still there. So doing some additional research on the ip command in BusyBox, I found out it crashes when dealing with IPv6 address information. Route information works well and also there is no error when giving the -4 option to include only IPv4 addresses.

I'll work a little on this to make it work somehow ;)

But still: does it hurt when images get larger then this 0x3a0000 limit?