New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#1891 - ar71xx kernel bump to 4.14 causes phase1 buildbot to fail for soem devices (kernel is too big) #6838
Comments
lister-wrt: I have this issue with tl-wr902ac-v1 too, doesn't look like the buildbot got that far. It was discussed briefly on the forum (https://forum.openwrt.org/t/plans-for-openwrt-to-support-tp-link-tl-wr902ac/3112/124). |
xback: Ill check it asap tomorrow |
xback: Hi Hannu, I pushed a fix to master for ens202ext and koala, moving them to Tiny which is an excellent proposal. Could you inform me if the buildbots finds more on the latest state? Thanks, Koen |
hardfalcon: Looks like two devices are breaking the build process for ar71xx/tiny snapshot images for two weeks now: https://phase1.builds.lede-project.org/builders/ar71xx%2Ftiny/builds/401/steps/images/logs/stdio The origin of the build problems for the ar71xx/generic targets seems exactly the same: https://phase1.builds.lede-project.org/builders/ar71xx%2Fgeneric/builds/988/steps/images/logs/stdio Is there any reason why there are predefined maximum kernel sizes on these devices at all? Don't they all use OpenWRT's u-boot build anyhow, just as the other ar71xx devices without kernel size limitation, so there's no real need for that artificial limitation after all? |
hnyman: Looking at the latest build log at buildbot ar71xx/generic, there are still 9 devices producing "is too big" errors: http://phase1.builds.lede-project.org/builders/ar71xx%2Fgeneric/builds/989/steps/images/logs/stdio
WARNING: Image file .../linux-ar71xx_generic/ap91-5g-kernel.bin is too big
WARNING: Image file .../linux-ar71xx_generic/ubnt-uap-pro-kernel.bin is too big
WARNING: Image file .../linux-ar71xx_generic/ubnt-unifi-outdoor-plus-kernel.bin is too big
WARNING: Image file .../linux-ar71xx_generic/tmp/openwrt-ar71xx-generic-archer-c7-v4-squashfs-sysupgrade.bin is too big
WARNING: Image file .../linux-ar71xx_generic/tmp/openwrt-ar71xx-generic-archer-c7-v5-squashfs-sysupgrade.bin is too big
WARNING: Image file .../linux-ar71xx_generic/tmp/openwrt-ar71xx-generic-re355-v1-squashfs-sysupgrade.bin is too big
WARNING: Image file .../linux-ar71xx_generic/tmp/openwrt-ar71xx-generic-re450-v1-squashfs-sysupgrade.bin is too big
WARNING: Image file .../linux-ar71xx_generic/tmp/openwrt-ar71xx-generic-tl-wr1043n-v5-squashfs-sysupgrade.bin is too big
WARNING: Image file .../linux-ar71xx_generic/tmp/openwrt-ar71xx-generic-tl-wr942n-v1-squashfs-sysupgrade.bin is too big
I am not quite sure if the sysupgrade images errors break the buildbot build, but the kernel bin errors likely do. In any case, no succesful buildbot build for ar71xx/generic has been made since the bump to 4.14 Ps. regarding tiny: |
oldium: Regarding TP-link targets (Archer, TL-WRxxx) - I got the same during local build of git main on Archer C7 V4, the problem is shown in the following message:
There are two places, where I found flash layout:
Simply changing //only// the values in tplink-safeloader did not make the image to boot on my Archer C7 V4, though (but the image built successfully), so maybe both need to be changed/synchronized - but I do not understand internals, so I really don't know. |
xback: Hi Oldfich, I've got a bunch of fixes in my staging tree. (including C7-V4) git://git.openwrt.org/openwrt/staging/xback.git Thanks |
oldium: Good, I will test it. Thanks. |
oldium: Looks good, Archer C7 V4 firmware builds (which is good), boots (which is great) and is usable (which is awesome) :-) |
xback: excellent Koen |
hnyman: Koen, |
xback: Hannu, yes, it should be enough as the fix mostly the same mor all other affected. The tiny targets (2 of them) will need to be disabled currently still. Koen |
xback: Hannu, Fixes pushed to master |
hnyman: Koen, tiny is still failing in buildbot, due to just two devices: linux-ar71xx_tiny/bhr-4grv2-kernel.bin is too big Maybe you should you disable them as a temporary measure. |
xback: Fix pushed to master to disable these targets. I waited to do this for some time, hoping to find an alternative to actually fix it, Looking at the size of kernel 4.19 .. they will probably remain disabled. Ps. |
WBINVD: A different and intermittent problem is affecting ramips/76x8. |
xback: Yes, And also gemini/generic. I can simulate both easily, but didnt findvyet why they lock-up. Ill take another look asap. |
xback: ar71xx/tiny confirmed fixed. https://phase1.builds.lede-project.org/builders/ar71xx%2Ftiny |
hnyman:
ar71xx kernel bump to 4.14 causes phase1 buildbot to fail for soem devices (kernel is too big)
http://phase1.builds.lede-project.org/builders/ar71xx%2Fgeneric/builds/973/steps/images/logs/stdio
Generic:
WARNING: ...ar71xx_generic/ap91-5g-kernel.bin is too big
WARNING: ...ar71xx_generic/ens202ext-kernel.bin is too big
WARNING: ...ar71xx_generic/koala-kernel.bin is too big
WARNING: ...ar71xx_generic/ubnt-uap-pro-kernel.bin is too big
WARNING: ...ar71xx_generic/ubnt-unifi-outdoor-plus-kernel.bin is too big
Those might need to be moved to "ar71xx-tiny" target.
Ps. There is more breakage in "ar71xx-tiny" target.
The text was updated successfully, but these errors were encountered: