On Wed, Nov 21, 2018 at 4:17 PM Daniel Díaz daniel.diaz@linaro.org wrote:

Hello!

On Mon, 19 Nov 2018 at 00:23, ci_notify@linaro.org wrote:

...

Build URL: https://ci.linaro.org/job/openembedded-lkft-linux-next/DISTRO=rpb,MACHINE=dr... Full log: https://ci.linaro.org/job/openembedded-lkft-linux-next/DISTRO=rpb,MACHINE=dr... Parsed warnings/errors: https://ci.linaro.org/job/openembedded-lkft-linux-next/DISTRO=rpb,MACHINE=dr... Git branch: master Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Git commit: f6de4a2389a4bcaf0e86e65a4ccc0d19063a8a78

Errors: ERROR: linux-generic-next-4.19+gitAUTOINC+f6de4a2389-r0 do_deploy: Function failed: do_deploy (log file is located at /srv/oe/build/tmp-rpb-glibc/work/dragonboard_410c-linaro-linux/linux-generic-next/4.19+gitAUTOINC+f6de4a2389-r0/temp/log.do_deploy.22684) ERROR: Logfile of failure stored in: /srv/oe/build/tmp-rpb-glibc/work/dragonboard_410c-linaro-linux/linux-generic-next/4.19+gitAUTOINC+f6de4a2389-r0/temp/log.do_deploy.22684 ERROR: Task (/srv/oe/build/conf/../../layers/meta-96boards/recipes-kernel/linux/linux-generic-next_git.bb:do_deploy) failed with exit code '1'

We started noticing this failure as of next-20181119. Looks like a problem with dbtTool and qcs404: removed 'ipq8074-hk01.dtb' removed 'sdm845-mtp.dtb' Traceback (most recent call last): File "/srv/oe/build/tmp-rpb-glibc/work/dragonboard_410c-linaro-linux/linux-generic-next/4.19+gitAUTOINC+f6de4a2389-r0/recipe-sysroot-native/usr/bin/skales/dtbTool", line 433, in <module> records += generate_records(f, pagesize) File "/srv/oe/build/tmp-rpb-glibc/work/dragonboard_410c-linaro-linux/linux-generic-next/4.19+gitAUTOINC+f6de4a2389-r0/recipe-sysroot-native/usr/bin/skales/dtbTool", line 386, in generate_records if QcomIds.pattern.match(compat)] File "/srv/oe/build/tmp-rpb-glibc/work/dragonboard_410c-linaro-linux/linux-generic-next/4.19+gitAUTOINC+f6de4a2389-r0/recipe-sysroot-native/usr/bin/skales/dtbTool", line 239, in __init__ self.msm_id[0] = soc_ids[matches['soc']] | (foundry << 16) KeyError: u'qcs404'

Does this ring any bells?

yes. that means that dtbTool does not support qcs404 , which is a new platform that landed in -next a few days ago. we stopped using dtbTool one year ago, since it is no longer supported by Qualcomm. dtbTool was a convenience tool published by Qualcomm to post process DTBs and insert some customs IDs in the DTB. These IDs are later used by the bootloader on the target to validate that the DTB corresponds to the actual target.. this 'MSM ID' mechanism has existed for Qualcomm kernel/bootloader for many years (it even predates device tree). Up until recently there were 2 choices:

1. include the msm ID in the DTS for each board, before compiling. that approach was rejected upstream (for good reasons). so that means folks testing upstream would need to apply patches manually. 2. use dtbTool that post processes the DTB and insert the proper MSM ID. that also means that dtbTool has a 'map' of all known SoC and their ID. So each time we added a new platform, dtbTool was updated with the corresponding id.

Maybe 1 year ago, we updated the bootloader on DB410c and DB820c so that we don't need to use dtbTool, at least on these 2 platforms. the way it works is that if 1 DTB (and just 1) is appended to the kernel image, then the bootloader (LK) will pass this DTB to the kernel *without* checking the MSM ID. Essentially that allows anyone to boot mainline 'easily' without MSM id and without dtbTool.

I would recommend you switch to this method, which also requires you have a 'recent' version of LK bootloader on your devices. It was implemented in September 2017.. so chances are that your bootloader already has that.

Greetings!

Daniel Díaz daniel.diaz@linaro.org