linaro-validation April 2013

linaro-validation@lists.linaro.org

29 participants
31 discussions

Re: [Linaro-validation] "android_install_binaries" failure after "deploy_linaro_android_image"

by Leo Wu

Hi Tyler: Thanks your information, it is useful. For current status, i can pass "android_install_binaries" but getting stuck in "boot_linaro_android_image". I think the problem is still relevant to panda-driver. This web have four files about pandaboard driver you posted( https://developers.google.com/android/nexus/drivers) 20111114 20111216 20120430 20120807 i dont know which one is suitable for my pandaboard so i have tried everyone. There have no one can pass "boot_linaro_android_image". The Log as following... LOG: 20111114: [ 521.131805] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 521.202728] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 521.552642] init: untracked pid 3766 exited [ 521.626464] init: untracked pid 3762 exited LEO COMMENT: PVR_K error. Does this driver not suitable for my pandaboard? 20111216 linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 37.700134] PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [4812, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 38.766967] init: untracked pid 1771 exited [ 41.124938] init: untracked pid 1774 exited LEO COMMENT: It looks like same as 20111114. 20120430: <LAVA_DISPATCHER>2013-03-27 02:30:45 PM DEBUG: expect (1800): '['Displayed com.android.launcher/com.android.launcher2.Launcher:']' logcat -s ActivityManager:I --------- beginning of /dev/log/main --------- beginning of /dev/log/system [ 96.093536] warning: `zygote' uses 32-bit capabilities (legacy support in use) I/ActivityManager( 1776): Memory class: 48 I/ActivityManager( 1776): Enabled StrictMode logging for AThread's Looper LEO COMMENT: No error message on this version. But it hang up and no more message print out. No console command line when i click "enter" key. 20120807: [ 53.677490] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4836, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 53.737884] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4836, /mnt/jenkins/workspace/linaro-android-member-ti_panda-linaro-13.02-release/build/kernel/drivers/gpu/pvr/bridged_pvr_bridge.c] [ 54.163696] init: untracked pid 1781 exited [ 55.792907] init: untracked pid 1784 exited LEO COMMENT: It looks like same as 20111114. One thing need to be mentiond, there have no "pvrsrvinit" but "pvrsrvctl" in version 20120807. Both files are same? LEO On 26 March 2013 20:57, Tyler Baker <tyler.baker(a)linaro.org> wrote: > Hi Leo Wu, > > The "android_install_binaries" dispatcher command will download, unpack, > and deploy proprietary shared objects to the Android file system. > > You can get these binaries from here: > https://developers.google.com/android/nexus/drivers - Choose the correct > binaries based on your Android build target. > > You will then have to create the following directory structure and tgz it: > > ./bin: > pvrsrvinit > > ./vendor: > lib > > ./vendor/lib: > egl hw libglslcompiler.so libIMGegl.so libpvr2d.so > libpvrANDROID_WSEGL.so libPVRScopeServices.so libsrv_init.so > libsrv_um.so libusc.so > > ./vendor/lib/egl: > libEGL_POWERVR_SGX540_120.so libGLESv1_CM_POWERVR_SGX540_120.so > libGLESv2_POWERVR_SGX540_120.so > > ./vendor/lib/hw: > gralloc.omap4.so > > At this point you have created your own panda-driver.tgz > > Now you will need to host it on a web server/file system that your LAVA > server can access. > > For instance, my LAVA server has the following defined: > > android_binary_drivers = http://192.168.1.2/panda-drivers.tgz <-- You > have to host this URL > > Hopefully this clears up any confusion you may have. Thanks. > > > > > > > On 26 March 2013 02:15, Leo Wu <leo.wu(a)linaro.org> wrote: > >> hi: >> Does anyone knows how to use "android_install_binaries" command in json >> file? Please give me some suggestion. >> I am trying to perfome lava android test on pandaboard. Currently, i face >> a problem while json file execute "android_install_binaries". >> The log shows it tries to connect to >> http://192.168.1.21/LAVA_HTTP/android-binaries/panda-drivers.tgz. >> >> log: http://192.168.1.21/LAVA_HTTP/android-binaries/panda-drivers.tgz Connecting >> to 192.168.1.21:80... failed:Connection timed out. >> RuntimeError: Extracting >> http://192.168.1.21/LAVA_HTTP/android-binaries/panda-drivers.tgz on >> target failed >> >> LAVA SERVER IP: 222.222.222.4 >> Board: pandaboard >> Master Image: Linaro PreBuild Image >> Test Image: LEB android >> >> >> 1. My LAVA SERVER ip is 222.222.222.4. i confused that why it tries to >> connect to 192.168.1.21? >> 2. what is panda-drivers.tgz? is it exist in lava server already or i >> need to download panda-drivers.tgz from somewhere by manual and stored it >> in local at first? >> 3. how to configure it? >> >> Thank you >> Leo >> >> _______________________________________________ >> linaro-validation mailing list >> linaro-validation(a)lists.linaro.org >> http://lists.linaro.org/mailman/listinfo/linaro-validation >> >> > > > -- > Tyler Baker > Technical Architect, Automation & CI > Linaro.org | Open source software for ARM SoCs > Follow Linaro: http://www.facebook.com/pages/Linaro > http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog >

12 years, 8 months

testing lab failover today

by Michael Hudson-Doyle

Hi all, I'm going to test some scripts I wrote to fail the LAVA database over to another server in a couple of hours (we will use this during the upgrade of precise to control too). This will cause two forms of disruption: 1) I've already offlined all boards and am waiting for the jobs to finish, so you might have to wait a little longer for your LAVA jobs to finish. 2) There will be some very short moments of complete outage as the failover happens. Apologies in advance if this causes you difficulties -- but I hope having better disaster recovery for the lab is a good goal :-) Cheers, mwh

13 years

Kernel-CI: Every thing is in RED

by Naresh Kamboju

Hi, I would like to inform you that, All Kernel-CI builds are in RED. Links: -------- - https://ci.linaro.org/jenkins/ - https://ci.linaro.org/jenkins/job/linux-next/ - https://ci.linaro.org/jenkins/job/linux-mainline/ - https://ci.linaro.org/jenkins/job/linux-arm-soc-for-next/ - ... Build error log: ------------------- https://ci.linaro.org/jenkins/job/linux-next/hwpack=multiplatform,label=pre… 00:35:24 + export toolchain_url=https://releases.linaro.org/13.03/components/toolchain/binari… 00:35:24 + bzr branch lp:linaro-ci lci-build-tools 00:35:25 bzr: ERROR: Invalid http response for https://xmlrpc.launchpad.net/bazaar/: Unable to handle http code 503: Service Unavailable 00:35:25 + cleanup_exit 00:35:25 + cd /mnt/ci_build/workspace/linux-next/hwpack/multiplatform/label/precise_hwpack_cloud 00:35:25 + rm -rf lci-build-tools 00:35:25 + rm -rf builddir* 00:35:25 Build step 'Execute shell' marked build as failure 00:35:25 Finished: FAILURE Best regards Naresh Kamboju

13 years, 1 month

Re: [Linaro-validation] Document related Web UI of LAVA

by Dave Pigott

(cc'ing validation list for wider advice) Hi Arthur, The only documentation I'm aware of is at http://lava.readthedocs.org/en/latest/components.html, but as you can see it's more of an overview. You might also start at http://www.linaro.org/engineering/validation and see if you find what you're looking for. What specifically are you trying to achieve? Different views/reports? Thanks Dave On 17 Apr 2013, at 09:42, Arthur.She <Arthur.She(a)tw.fujitsu.com> wrote: > Hi Dave, > This is Arthur from Fujitsu. Something related LAVA we need to consult with you. > Is there any document describe LAVA Server (dashboard and scheduler). > I mean something like user guide or user manual. > Currently, we have 4 DUTs in our LAVA test farm (2 kinds, one Panda board and 3 our EVB - V2). > In order to adapt our EVB into LAVA, we added a new module v2.py and did some modification with lava-dispatcher. Right now, we can have DUTs (both Panda board and our EVB) tested by the command "lava-dispatch". > Beside the command line, we would like to know if there any document we can reference regarding the Web UI of LAVA server? > > > Thanks a lot & Best Regards, > Arthur

13 years, 1 month

Help with solving ubuntu hardware pack issues on LAVA...

by Basil Eljuse

Hi, Apologies for a long email to start with! We are trying to get locally generated kernel images used for testing on Ubuntu config via LAVA. The failure we see on LAVA is root@master [rc=0]# <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: [ACTION-E] deploy_linaro_image is finished successfully. <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: [ACTION-B] lava_test_install is started with {u'tests': [u'ltp', u'pwrmgmt'], u'timeout': 4000} <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Executing lava_test_install (ltp,pwrmgmt) command <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Boot the test image <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: boot_cmds attribute: boot_cmds <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Perform soft reboot the system 'after soft reboot' [1] LAVA Master Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/zImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/uInitrd - Arguments: console=ttyAMA0,38400n8 root=/dev/mmcblk0p2 rootwait ro - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/tc2_dtb.bin - LoaderType: Linux kernel with Local FDT [2] LAVA Ubuntu Test Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uInitrd - Arguments: console=ttyAMA0,38400n8 root=/dev/mmcblk0p5 rootwait ro - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb - LoaderType: Linux kernel with Local FDT [3] LAVA Android Test Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uInitrd - Arguments: console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init androidboot.console=ttyAMA0 - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb - LoaderType: Linux kernel with Local FDT ----------------------- Global FDT Config - VenHw(1F15DA3C-37FF-4070-B471-BB4AF12A724A)/MemoryMapped(0x0,0xE800000,0xE803000) ----------------------- [a] Boot Manager [b] Shell Start: 2 ERROR: Did not find Device Tree blob. ASSERT /linaro/lt/uefi/uefi-next.git/edk2/MdeModulePkg/Core/Dxe/Mem/Pool.c(424): CR has Bad Signature <LAVA_DISPATCHER>2013-04-26 09:55:46 PM WARNING: Sending newline in case of corruption. What is being done:: Once the Ubuntu .deb packages are generated we are fetching existing hardware pack from https://releases.linaro.org/13.03/ubuntu/vexpress/hwpack_linaro-vexpress_20… And replacing our linux-image package in the hardware pack using ./linaro-image-tools/linaro-hwpack-replace -t hwpack_linaro-vexpress_20130426-1528_armhf_supported.tar.gz -p linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb -r linux-image-3.9 -d (Initially we did the mistake of specifying '-r linux-image' which meant it was removing more than the intended number of packages as more than one package has the specified prefix!) By comparing the hardware pack tar ball before and after the above command I could see that linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/pkgs/linux-image-3.9.0-1-linaro-…> is replaced with linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/undertest/pkgs/linux-image-3.9.0…> Also i tried to list the contents of linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/pkgs/linux-image-3.9.0-1-linaro-…> and compare against contents of linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/undertest/pkgs/linux-image-3.9.0…> contents of linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb contents of linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb ----------------------------------------------------------- ----------------------------------------------------------- drwxr-xr-x root/root 0 2013-03-23 15:43 ./ drwxr-xr-x root/root 0 2013-04-26 11:56 ./ drwxr-xr-x root/root 0 2013-03-23 15:43 ./boot/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/ -rw------- root/root 4465976 2013-03-23 15:43 ./boot/vmlinuz-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/ -rw------- root/root 1620900 2013-03-23 15:43 ./boot/System.map-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/preinst.d/ -rw-r--r-- root/root 53455 2013-03-23 15:43 ./boot/config-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/postinst.d/ -rw-r--r-- root/root 300000 2013-03-23 15:43 ./boot/abi-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/postrm.d/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/prerm.d/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/share/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/share/doc/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/ drwxr-xr-x root/root 0 2013-03-23 15:46 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/doc/ -rw-r--r-- root/root 715 2013-03-23 13:37 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/changelog.Debian.gz drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/ -rw-r--r-- root/root 1292 2013-03-23 13:37 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/copyright -rw-r--r-- root/root 690 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/copyright -rw-r--r-- root/root 715 2013-03-23 15:43 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/changelog.Debian.old.gz -rw-r--r-- root/root 175 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/changelog.Debian.gz drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./boot/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/ -rw-r--r-- root/root 56813 2013-04-26 11:56 ./boot/config-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:46 ./lib/modules/3.9.0-1-linaro-vexpress/ -rwxr-xr-x root/root 3776056 2013-04-26 11:56 ./boot/vmlinuz-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/ -rw-r--r-- root/root 1544394 2013-04-26 11:56 ./boot/System.map-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/crypto/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/ -rw-r--r-- root/root 8776 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/crypto/ansi_cprng.ko drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/ -rw-r--r-- root/root 189 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.usbmap drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/hw_random/ -rw-r--r-- root/root 103 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.dep -rw-r--r-- root/root 7644 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/hw_random/rng-core.ko -rw-r--r-- root/root 52 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.devname drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/gator/ -rw-r--r-- root/root 69 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.alias -rw-r--r-- root/root 85708 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/gator/gator.ko -rw-r--r-- root/root 43 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.seriomap -rw-r--r-- root/root 5400 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/modules.builtin -rw-r--r-- root/root 100 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.order drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/initrd/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/ -rw-r--r-- root/root 100 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/modules.order drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/hw_random/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/ -rw-r--r-- root/root 7761 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/hw_random/rng-core.ko -rw-r--r-- root/root 8778 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a9x4.dtb drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/gator/ -rw-r--r-- root/root 11176 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-v2p-ca15x4-ca7x4.dtb -rw-r--r-- root/root 76195 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/gator/gator.ko -rw-r--r-- root/root 11369 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15-tc1.dtb drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/crypto/ -rw-r--r-- root/root 12408 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15_a7.dtb -rw-r--r-- root/root 7818 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/crypto/ansi_cprng.ko -rw-r--r-- root/root 12940 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca9.dtb -rw-r--r-- root/root 69 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ccwmap -rw-r--r-- root/root 8718 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x4.dtb -rw-r--r-- root/root 690 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.symbols -rw-r--r-- root/root 9472 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-v2p-ca15x1-ca7x1.dtb -rw-r--r-- root/root 43 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.alias.bin -rw-r--r-- root/root 1056 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/xenvm-4.2.dtb -rw-r--r-- root/root 131 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.softdep -rw-r--r-- root/root 8566 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x2.dtb -rw-r--r-- root/root 141 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.inputmap -rw-r--r-- root/root 14469 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15-tc2.dtb -rw-r--r-- root/root 5632 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.builtin -rw-r--r-- root/root 8626 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a9x2.dtb -rw-r--r-- root/root 74 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ofmap -rw-r--r-- root/root 10802 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca5s.dtb -rw-r--r-- root/root 236 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.dep.bin -rw-r--r-- root/root 8490 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x1.dtb -rw-r--r-- root/root 99 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.pcimap -rw-r--r-- root/root 81 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.isapnpmap -rw-r--r-- root/root 615 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.symbols.bin -rw-r--r-- root/root 7211 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.builtin.bin -rw-r--r-- root/root 73 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ieee1394map drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/ -rw-r--r-- root/root 14453 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15_a7.dtb -rw-r--r-- root/root 8778 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a9x4.dtb -rw-r--r-- root/root 8718 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x4.dtb -rw-r--r-- root/root 8626 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a9x2.dtb -rw-r--r-- root/root 12892 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca9.dtb -rw-r--r-- root/root 9472 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-v2p-ca15x1-ca7x1.dtb -rw-r--r-- root/root 13665 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a15only.dtb -rw-r--r-- root/root 10786 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca5s.dtb -rw-r--r-- root/root 13933 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a7only.dtb -rw-r--r-- root/root 1056 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/xenvm-4.2.dtb -rw-r--r-- root/root 11176 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-v2p-ca15x4-ca7x4.dtb -rw-r--r-- root/root 8490 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x1.dtb -rw-r--r-- root/root 14469 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a7bootcluster.dtb -rw-r--r-- root/root 8566 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x2.dtb -rw-r--r-- root/root 11349 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc1.dtb Does lava expects tc2 dtb with some specific name? In uefi we have got the following set for Ubuntu test image. - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb However we do have health check jobs with Linaro generated hardware packs which get used without any modifications and they seem to work fine. Which makes me suspect probably, linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb should have dtb named as vexpress-v2p-ca15-tc2.dtb? Any help is much appreciated. Thanks Basil Eljuse... -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

13 years, 1 month

Re: [Linaro-validation] Help with solving ubuntu hardware pack issues on LAVA...

by Basil Eljuse

Forgot mention that when I list dpkg -content hwpack-linaro-vexpress_20130324-276_armhf.deb i get drwxrwxr-x ubuntu/ubuntu 0 2013-03-24 12:42 ./ Thanks Basil Eljuse... From: Basil Eljuse Sent: 29 April 2013 21:08 To: 'Dave Pigott' Cc: Linaro Validation; Liviu Dudau; Dean Arnold Subject: RE: [Linaro-validation] Help with solving ubuntu hardware pack issues on LAVA... Hi Dave, We tried with an updated linux-kernel*.deb which has got the same dtb name as -rw-r--r-- root/root 14469 2013-04-29 14:19 ./lib/firmware/3.9.0-rc7/device-tree/v2p-ca15-tc2.dtb Replaced in the hardware pack. But we still hit the same issue as UEFI complaining 'Device Tree not found' To me it is either down to the deb packages which we are generating or w.r.t the linaro-hwpack-replace usage. I compared the contents of the hardware pack tar ball before and after the hwpack-replace command Before hwpack-replace command After hwpack-replace command linux-headers-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb linux-headers-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb devio_1.2-1build2_armhf.deb devio_1.2-1build2_armhf.deb flash-kernel_3.0~rc.4ubuntu27.2~linaro1_armhf.deb flash-kernel_3.0~rc.4ubuntu27.2~linaro1_armhf.deb u-boot-linaro-vexpress-ca9x4_2012.08.2+6697+48+201211212230~precise1_armhf.deb u-boot-linaro-vexpress-ca9x4_2012.08.2+6697+48+201211212230~precise1_armhf.deb linux-headers-linaro-vexpress_3.9.0.1.1_armhf.deb linux-headers-linaro-vexpress_3.9.0.1.1_armhf.deb linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb u-boot-tools_2012.04.01-2_armhf.deb u-boot-tools_2012.04.01-2_armhf.deb ubuntu-vexpress-extras-config_0.3_all.deb ubuntu-vexpress-extras-config_0.3_all.deb grub-arm_2.00+bzr4618+20130322-0linaro1_armhf.deb grub-arm_2.00+bzr4618+20130322-0linaro1_armhf.deb linux-image-linaro-vexpress_3.9.0.1.1_armhf.deb linux-image-linaro-vexpress_3.9.0.1.1_armhf.deb linux-firmware_1.98~linaro1_all.deb linux-firmware_1.98~linaro1_all.deb uboot-mkimage_2012.04.01-2_all.deb uboot-mkimage_2012.04.01-2_all.deb libuuid-perl_0.02-4ubuntu2_armhf.deb libuuid-perl_0.02-4ubuntu2_armhf.deb uefi-image-vexpress_0.1+git11+20130222+d9875a6-0linaro1_armhf.deb uefi-image-vexpress_0.1+git11+20130222+d9875a6-0linaro1_armhf.deb linux-base_3.5ubuntu4_all.deb linux-base_3.5ubuntu4_all.deb kvm-boot-wrapper_0.1~ppa1+bzr48+bzr16~quantal1_armhf.deb kvm-boot-wrapper_0.1~ppa1+bzr48+bzr16~quantal1_armhf.deb hwpack-linaro-vexpress_20130324-276_armhf.deb Packages Packages I could see one additional .deb (in red) missing after the hwpack-replace command is issued. Any idea if the problems we see could be down to this. Any clue? Attaching the full LAVA run output if that helps. Thanks Basil Eljuse... From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 27 April 2013 09:54 To: Basil Eljuse Cc: Linaro Validation; Liviu Dudau; Dean Arnold Subject: Re: [Linaro-validation] Help with solving ubuntu hardware pack issues on LAVA... On 26 Apr 2013, at 23:32, Basil Eljuse <Basil.Eljuse(a)arm.com<mailto:Basil.Eljuse@arm.com>> wrote: Hi, Apologies for a long email to start with! We are trying to get locally generated kernel images used for testing on Ubuntu config via LAVA. The failure we see on LAVA is root@master [rc=0]# <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: [ACTION-E] deploy_linaro_image is finished successfully. <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: [ACTION-B] lava_test_install is started with {u'tests': [u'ltp', u'pwrmgmt'], u'timeout': 4000} <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Executing lava_test_install (ltp,pwrmgmt) command <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Boot the test image <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: boot_cmds attribute: boot_cmds <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Perform soft reboot the system 'after soft reboot' [1] LAVA Master Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/zImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/uInitrd - Arguments: console=ttyAMA0,38400n8 root=/dev/mmcblk0p2 rootwait ro - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/tc2_dtb.bin - LoaderType: Linux kernel with Local FDT [2] LAVA Ubuntu Test Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uInitrd - Arguments: console=ttyAMA0,38400n8 root=/dev/mmcblk0p5 rootwait ro - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb - LoaderType: Linux kernel with Local FDT [3] LAVA Android Test Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uInitrd - Arguments: console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init androidboot.console=ttyAMA0 - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb - LoaderType: Linux kernel with Local FDT ----------------------- Global FDT Config - VenHw(1F15DA3C-37FF-4070-B471-BB4AF12A724A)/MemoryMapped(0x0,0xE800000,0xE803000) ----------------------- [a] Boot Manager [b] Shell Start: 2 ERROR: Did not find Device Tree blob. ASSERT /linaro/lt/uefi/uefi-next.git/edk2/MdeModulePkg/Core/Dxe/Mem/Pool.c(424): CR has Bad Signature <LAVA_DISPATCHER>2013-04-26 09:55:46 PM WARNING: Sending newline in case of corruption. What is being done:: Once the Ubuntu .deb packages are generated we are fetching existing hardware pack from https://releases.linaro.org/13.03/ubuntu/vexpress/hwpack_linaro-vexpress_20… And replacing our linux-image package in the hardware pack using ./linaro-image-tools/linaro-hwpack-replace -t hwpack_linaro-vexpress_20130426-1528_armhf_supported.tar.gz -p linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb -r linux-image-3.9 -d (Initially we did the mistake of specifying '-r linux-image' which meant it was removing more than the intended number of packages as more than one package has the specified prefix!) By comparing the hardware pack tar ball before and after the above command I could see that linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/pkgs/linux-image-3.9.0-1-linaro-…> is replaced with linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/undertest/pkgs/linux-image-3.9.0…> Also i tried to list the contents of linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/pkgs/linux-image-3.9.0-1-linaro-…> and compare against contents of linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/undertest/pkgs/linux-image-3.9.0…> contents of linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb contents of linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb ----------------------------------------------------------- ----------------------------------------------------------- drwxr-xr-x root/root 0 2013-03-23 15:43 ./ drwxr-xr-x root/root 0 2013-04-26 11:56 ./ drwxr-xr-x root/root 0 2013-03-23 15:43 ./boot/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/ -rw------- root/root 4465976 2013-03-23 15:43 ./boot/vmlinuz-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/ -rw------- root/root 1620900 2013-03-23 15:43 ./boot/System.map-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/preinst.d/ -rw-r--r-- root/root 53455 2013-03-23 15:43 ./boot/config-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/postinst.d/ -rw-r--r-- root/root 300000 2013-03-23 15:43 ./boot/abi-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/postrm.d/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/prerm.d/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/share/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/share/doc/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/ drwxr-xr-x root/root 0 2013-03-23 15:46 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/doc/ -rw-r--r-- root/root 715 2013-03-23 13:37 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/changelog.Debian.gz drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/ -rw-r--r-- root/root 1292 2013-03-23 13:37 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/copyright -rw-r--r-- root/root 690 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/copyright -rw-r--r-- root/root 715 2013-03-23 15:43 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/changelog.Debian.old.gz -rw-r--r-- root/root 175 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/changelog.Debian.gz drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./boot/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/ -rw-r--r-- root/root 56813 2013-04-26 11:56 ./boot/config-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:46 ./lib/modules/3.9.0-1-linaro-vexpress/ -rwxr-xr-x root/root 3776056 2013-04-26 11:56 ./boot/vmlinuz-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/ -rw-r--r-- root/root 1544394 2013-04-26 11:56 ./boot/System.map-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/crypto/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/ -rw-r--r-- root/root 8776 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/crypto/ansi_cprng.ko drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/ -rw-r--r-- root/root 189 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.usbmap drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/hw_random/ -rw-r--r-- root/root 103 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.dep -rw-r--r-- root/root 7644 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/hw_random/rng-core.ko -rw-r--r-- root/root 52 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.devname drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/gator/ -rw-r--r-- root/root 69 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.alias -rw-r--r-- root/root 85708 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/gator/gator.ko -rw-r--r-- root/root 43 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.seriomap -rw-r--r-- root/root 5400 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/modules.builtin -rw-r--r-- root/root 100 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.order drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/initrd/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/ -rw-r--r-- root/root 100 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/modules.order drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/hw_random/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/ -rw-r--r-- root/root 7761 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/hw_random/rng-core.ko -rw-r--r-- root/root 8778 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a9x4.dtb drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/gator/ -rw-r--r-- root/root 11176 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-v2p-ca15x4-ca7x4.dtb -rw-r--r-- root/root 76195 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/gator/gator.ko -rw-r--r-- root/root 11369 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15-tc1.dtb drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/crypto/ -rw-r--r-- root/root 12408 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15_a7.dtb -rw-r--r-- root/root 7818 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/crypto/ansi_cprng.ko -rw-r--r-- root/root 12940 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca9.dtb -rw-r--r-- root/root 69 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ccwmap -rw-r--r-- root/root 8718 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x4.dtb -rw-r--r-- root/root 690 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.symbols -rw-r--r-- root/root 9472 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-v2p-ca15x1-ca7x1.dtb -rw-r--r-- root/root 43 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.alias.bin -rw-r--r-- root/root 1056 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/xenvm-4.2.dtb -rw-r--r-- root/root 131 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.softdep -rw-r--r-- root/root 8566 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x2.dtb -rw-r--r-- root/root 141 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.inputmap -rw-r--r-- root/root 14469 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15-tc2.dtb -rw-r--r-- root/root 5632 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.builtin -rw-r--r-- root/root 8626 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a9x2.dtb -rw-r--r-- root/root 74 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ofmap -rw-r--r-- root/root 10802 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca5s.dtb -rw-r--r-- root/root 236 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.dep.bin -rw-r--r-- root/root 8490 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x1.dtb -rw-r--r-- root/root 99 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.pcimap -rw-r--r-- root/root 81 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.isapnpmap -rw-r--r-- root/root 615 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.symbols.bin -rw-r--r-- root/root 7211 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.builtin.bin -rw-r--r-- root/root 73 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ieee1394map drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/ -rw-r--r-- root/root 14453 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15_a7.dtb -rw-r--r-- root/root 8778 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a9x4.dtb -rw-r--r-- root/root 8718 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x4.dtb -rw-r--r-- root/root 8626 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a9x2.dtb -rw-r--r-- root/root 12892 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca9.dtb -rw-r--r-- root/root 9472 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-v2p-ca15x1-ca7x1.dtb -rw-r--r-- root/root 13665 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a15only.dtb -rw-r--r-- root/root 10786 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca5s.dtb -rw-r--r-- root/root 13933 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a7only.dtb -rw-r--r-- root/root 1056 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/xenvm-4.2.dtb -rw-r--r-- root/root 11176 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-v2p-ca15x4-ca7x4.dtb -rw-r--r-- root/root 8490 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x1.dtb -rw-r--r-- root/root 14469 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a7bootcluster.dtb -rw-r--r-- root/root 8566 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x2.dtb -rw-r--r-- root/root 11349 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc1.dtb Does lava expects tc2 dtb with some specific name? In uefi we have got the following set for Ubuntu test image. - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb However we do have health check jobs with Linaro generated hardware packs which get used without any modifications and they seem to work fine. Which makes me suspect probably, linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb should have dtb named as vexpress-v2p-ca15-tc2.dtb? Any help is much appreciated. Basically, you're right, in that whatever is configured in UEFI boot options 2 and 3 must match the dtb name of the image. The simplest solution is for your hwpack to have its dtb name be v2p-ca15-tc2.dtb so that it's consistent with the Linaro health check. The other alternative is to use your own hwpack for a health check job and then change it to the above. Thanks Dave -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

13 years, 1 month

Re: [Linaro-validation] Help with solving ubuntu hardware pack issues on LAVA...

by Basil Eljuse

Hi Dave, We tried with an updated linux-kernel*.deb which has got the same dtb name as -rw-r--r-- root/root 14469 2013-04-29 14:19 ./lib/firmware/3.9.0-rc7/device-tree/v2p-ca15-tc2.dtb Replaced in the hardware pack. But we still hit the same issue as UEFI complaining 'Device Tree not found' To me it is either down to the deb packages which we are generating or w.r.t the linaro-hwpack-replace usage. I compared the contents of the hardware pack tar ball before and after the hwpack-replace command Before hwpack-replace command After hwpack-replace command linux-headers-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb linux-headers-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb devio_1.2-1build2_armhf.deb devio_1.2-1build2_armhf.deb flash-kernel_3.0~rc.4ubuntu27.2~linaro1_armhf.deb flash-kernel_3.0~rc.4ubuntu27.2~linaro1_armhf.deb u-boot-linaro-vexpress-ca9x4_2012.08.2+6697+48+201211212230~precise1_armhf.deb u-boot-linaro-vexpress-ca9x4_2012.08.2+6697+48+201211212230~precise1_armhf.deb linux-headers-linaro-vexpress_3.9.0.1.1_armhf.deb linux-headers-linaro-vexpress_3.9.0.1.1_armhf.deb linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb u-boot-tools_2012.04.01-2_armhf.deb u-boot-tools_2012.04.01-2_armhf.deb ubuntu-vexpress-extras-config_0.3_all.deb ubuntu-vexpress-extras-config_0.3_all.deb grub-arm_2.00+bzr4618+20130322-0linaro1_armhf.deb grub-arm_2.00+bzr4618+20130322-0linaro1_armhf.deb linux-image-linaro-vexpress_3.9.0.1.1_armhf.deb linux-image-linaro-vexpress_3.9.0.1.1_armhf.deb linux-firmware_1.98~linaro1_all.deb linux-firmware_1.98~linaro1_all.deb uboot-mkimage_2012.04.01-2_all.deb uboot-mkimage_2012.04.01-2_all.deb libuuid-perl_0.02-4ubuntu2_armhf.deb libuuid-perl_0.02-4ubuntu2_armhf.deb uefi-image-vexpress_0.1+git11+20130222+d9875a6-0linaro1_armhf.deb uefi-image-vexpress_0.1+git11+20130222+d9875a6-0linaro1_armhf.deb linux-base_3.5ubuntu4_all.deb linux-base_3.5ubuntu4_all.deb kvm-boot-wrapper_0.1~ppa1+bzr48+bzr16~quantal1_armhf.deb kvm-boot-wrapper_0.1~ppa1+bzr48+bzr16~quantal1_armhf.deb hwpack-linaro-vexpress_20130324-276_armhf.deb Packages Packages I could see one additional .deb (in red) missing after the hwpack-replace command is issued. Any idea if the problems we see could be down to this. Any clue? Attaching the full LAVA run output if that helps. Thanks Basil Eljuse... From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 27 April 2013 09:54 To: Basil Eljuse Cc: Linaro Validation; Liviu Dudau; Dean Arnold Subject: Re: [Linaro-validation] Help with solving ubuntu hardware pack issues on LAVA... On 26 Apr 2013, at 23:32, Basil Eljuse <Basil.Eljuse(a)arm.com<mailto:Basil.Eljuse@arm.com>> wrote: Hi, Apologies for a long email to start with! We are trying to get locally generated kernel images used for testing on Ubuntu config via LAVA. The failure we see on LAVA is root@master [rc=0]# <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: [ACTION-E] deploy_linaro_image is finished successfully. <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: [ACTION-B] lava_test_install is started with {u'tests': [u'ltp', u'pwrmgmt'], u'timeout': 4000} <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Executing lava_test_install (ltp,pwrmgmt) command <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Boot the test image <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: boot_cmds attribute: boot_cmds <LAVA_DISPATCHER>2013-04-26 09:52:37 PM INFO: Perform soft reboot the system 'after soft reboot' [1] LAVA Master Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/zImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/uInitrd - Arguments: console=ttyAMA0,38400n8 root=/dev/mmcblk0p2 rootwait ro - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x2000,0x1A000)/tc2_dtb.bin - LoaderType: Linux kernel with Local FDT [2] LAVA Ubuntu Test Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uInitrd - Arguments: console=ttyAMA0,38400n8 root=/dev/mmcblk0p5 rootwait ro - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb - LoaderType: Linux kernel with Local FDT [3] LAVA Android Test Image - VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uImage - Initrd: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/uInitrd - Arguments: console=tty0 console=ttyAMA0,38400n8 rootwait ro init=/init androidboot.console=ttyAMA0 - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb - LoaderType: Linux kernel with Local FDT ----------------------- Global FDT Config - VenHw(1F15DA3C-37FF-4070-B471-BB4AF12A724A)/MemoryMapped(0x0,0xE800000,0xE803000) ----------------------- [a] Boot Manager [b] Shell Start: 2 ERROR: Did not find Device Tree blob. ASSERT /linaro/lt/uefi/uefi-next.git/edk2/MdeModulePkg/Core/Dxe/Mem/Pool.c(424): CR has Bad Signature <LAVA_DISPATCHER>2013-04-26 09:55:46 PM WARNING: Sending newline in case of corruption. What is being done:: Once the Ubuntu .deb packages are generated we are fetching existing hardware pack from https://releases.linaro.org/13.03/ubuntu/vexpress/hwpack_linaro-vexpress_20… And replacing our linux-image package in the hardware pack using ./linaro-image-tools/linaro-hwpack-replace -t hwpack_linaro-vexpress_20130426-1528_armhf_supported.tar.gz -p linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb -r linux-image-3.9 -d (Initially we did the mistake of specifying '-r linux-image' which meant it was removing more than the intended number of packages as more than one package has the specified prefix!) By comparing the hardware pack tar ball before and after the above command I could see that linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/pkgs/linux-image-3.9.0-1-linaro-…> is replaced with linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/undertest/pkgs/linux-image-3.9.0…> Also i tried to list the contents of linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/pkgs/linux-image-3.9.0-1-linaro-…> and compare against contents of linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb<http://pdsw-jenkins:8080/job/test%20job/ws/undertest/pkgs/linux-image-3.9.0…> contents of linux-image-3.9.0-1-linaro-vexpress_3.9.0-1.1ubuntu1~ci+130323130056_armhf.deb contents of linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb ----------------------------------------------------------- ----------------------------------------------------------- drwxr-xr-x root/root 0 2013-03-23 15:43 ./ drwxr-xr-x root/root 0 2013-04-26 11:56 ./ drwxr-xr-x root/root 0 2013-03-23 15:43 ./boot/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/ -rw------- root/root 4465976 2013-03-23 15:43 ./boot/vmlinuz-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/ -rw------- root/root 1620900 2013-03-23 15:43 ./boot/System.map-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/preinst.d/ -rw-r--r-- root/root 53455 2013-03-23 15:43 ./boot/config-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/postinst.d/ -rw-r--r-- root/root 300000 2013-03-23 15:43 ./boot/abi-3.9.0-1-linaro-vexpress drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/postrm.d/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./etc/kernel/prerm.d/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/share/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./usr/share/doc/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/ drwxr-xr-x root/root 0 2013-03-23 15:46 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/doc/ -rw-r--r-- root/root 715 2013-03-23 13:37 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/changelog.Debian.gz drwxr-xr-x root/root 0 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/ -rw-r--r-- root/root 1292 2013-03-23 13:37 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/copyright -rw-r--r-- root/root 690 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/copyright -rw-r--r-- root/root 715 2013-03-23 15:43 ./usr/share/doc/linux-image-3.9.0-1-linaro-vexpress/changelog.Debian.old.gz -rw-r--r-- root/root 175 2013-04-26 11:56 ./usr/share/doc/linux-image-3.9.0-rc7/changelog.Debian.gz drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./boot/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/ -rw-r--r-- root/root 56813 2013-04-26 11:56 ./boot/config-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:46 ./lib/modules/3.9.0-1-linaro-vexpress/ -rwxr-xr-x root/root 3776056 2013-04-26 11:56 ./boot/vmlinuz-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/ -rw-r--r-- root/root 1544394 2013-04-26 11:56 ./boot/System.map-3.9.0-rc7 drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/crypto/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/ -rw-r--r-- root/root 8776 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/crypto/ansi_cprng.ko drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/ -rw-r--r-- root/root 189 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.usbmap drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/hw_random/ -rw-r--r-- root/root 103 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.dep -rw-r--r-- root/root 7644 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/char/hw_random/rng-core.ko -rw-r--r-- root/root 52 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.devname drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/gator/ -rw-r--r-- root/root 69 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.alias -rw-r--r-- root/root 85708 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/kernel/drivers/gator/gator.ko -rw-r--r-- root/root 43 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.seriomap -rw-r--r-- root/root 5400 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/modules.builtin -rw-r--r-- root/root 100 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.order drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/initrd/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/ -rw-r--r-- root/root 100 2013-03-23 15:43 ./lib/modules/3.9.0-1-linaro-vexpress/modules.order drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/hw_random/ drwxr-xr-x root/root 0 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/ -rw-r--r-- root/root 7761 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/char/hw_random/rng-core.ko -rw-r--r-- root/root 8778 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a9x4.dtb drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/gator/ -rw-r--r-- root/root 11176 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-v2p-ca15x4-ca7x4.dtb -rw-r--r-- root/root 76195 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/drivers/gator/gator.ko -rw-r--r-- root/root 11369 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15-tc1.dtb drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/crypto/ -rw-r--r-- root/root 12408 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15_a7.dtb -rw-r--r-- root/root 7818 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/kernel/crypto/ansi_cprng.ko -rw-r--r-- root/root 12940 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca9.dtb -rw-r--r-- root/root 69 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ccwmap -rw-r--r-- root/root 8718 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x4.dtb -rw-r--r-- root/root 690 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.symbols -rw-r--r-- root/root 9472 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-v2p-ca15x1-ca7x1.dtb -rw-r--r-- root/root 43 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.alias.bin -rw-r--r-- root/root 1056 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/xenvm-4.2.dtb -rw-r--r-- root/root 131 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.softdep -rw-r--r-- root/root 8566 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x2.dtb -rw-r--r-- root/root 141 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.inputmap -rw-r--r-- root/root 14469 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca15-tc2.dtb -rw-r--r-- root/root 5632 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.builtin -rw-r--r-- root/root 8626 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a9x2.dtb -rw-r--r-- root/root 74 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ofmap -rw-r--r-- root/root 10802 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/vexpress-v2p-ca5s.dtb -rw-r--r-- root/root 236 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.dep.bin -rw-r--r-- root/root 8490 2013-03-23 15:43 ./lib/firmware/3.9.0-1-linaro-vexpress/device-tree/rtsm_ve-cortex_a15x1.dtb -rw-r--r-- root/root 99 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.pcimap -rw-r--r-- root/root 81 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.isapnpmap -rw-r--r-- root/root 615 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.symbols.bin -rw-r--r-- root/root 7211 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.builtin.bin -rw-r--r-- root/root 73 2013-04-26 11:56 ./lib/modules/3.9.0-rc7/modules.ieee1394map drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/ drwxr-xr-x root/root 0 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/ -rw-r--r-- root/root 14453 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15_a7.dtb -rw-r--r-- root/root 8778 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a9x4.dtb -rw-r--r-- root/root 8718 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x4.dtb -rw-r--r-- root/root 8626 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a9x2.dtb -rw-r--r-- root/root 12892 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca9.dtb -rw-r--r-- root/root 9472 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-v2p-ca15x1-ca7x1.dtb -rw-r--r-- root/root 13665 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a15only.dtb -rw-r--r-- root/root 10786 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca5s.dtb -rw-r--r-- root/root 13933 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a7only.dtb -rw-r--r-- root/root 1056 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/xenvm-4.2.dtb -rw-r--r-- root/root 11176 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-v2p-ca15x4-ca7x4.dtb -rw-r--r-- root/root 8490 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x1.dtb -rw-r--r-- root/root 14469 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc2_a7bootcluster.dtb -rw-r--r-- root/root 8566 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/rtsm_ve-cortex_a15x2.dtb -rw-r--r-- root/root 11349 2013-04-26 11:56 ./lib/firmware/3.9.0-rc7/device-tree/vexpress-v2p-ca15-tc1.dtb Does lava expects tc2 dtb with some specific name? In uefi we have got the following set for Ubuntu test image. - FDT: VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(3,MBR,0x00000000,0x200000,0x20000)/v2p-ca15-tc2.dtb However we do have health check jobs with Linaro generated hardware packs which get used without any modifications and they seem to work fine. Which makes me suspect probably, linux-image-3.9.0-rc7_3.9.0-rc7-1_armhf.deb should have dtb named as vexpress-v2p-ca15-tc2.dtb? Any help is much appreciated. Basically, you're right, in that whatever is configured in UEFI boot options 2 and 3 must match the dtb name of the image. The simplest solution is for your hwpack to have its dtb name be v2p-ca15-tc2.dtb so that it's consistent with the Linaro health check. The other alternative is to use your own hwpack for a health check job and then change it to the above. Thanks Dave -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

13 years, 1 month

Re: [Linaro-validation] CI Runtime API

by James Tunnicliffe

On Fri Apr 26 02:25:14 UTC 2013 Antonio Terceiro replied to me, but I wasn't on the list, so only just spotted it in the web interface... > Non-API related thought: I think it is reasonable to have an internal >> file server to store disk images on that we create during builds >> without having to push up to snapshots.linaro.org and pull them back >> down. It makes far more sense to boot and test an image, then >> optionally upload it to the wider world. Let me know if we have this >> soft of temporary storage available. > We don't have something like this, but we probably should have one. >> I need to know if a machine is ready for me to use. I am happy to poll >> something. >> >> I need to tell LAVA/CI that I have finished with a machine. > If I understand correctly your asumption is to receive a interactive > session on the requested device(s), and then issue commands on it. Is > that correct? Yep Very similar to the LAVA hack tool that Tyler just demoed. > Maybe it's too late to ask this, but did you consider the possibility of > having the CI runtime produce "actual" LAVA jobs (i.e. a target device > spec + a non-interactive script), and then using an API to submit those > jobs, poll for their completion (or block until completion depending on > the use case) and acessing/manipulating/addressing the job results, > perhaps to use them as input for other jobs? I did consider a fixed function test approach, but for some jobs we are creating new commands based on the output of previous ones. It also restricts jobs to be a fixed sequence of commands unless you start implementing branches and loops in the test spec. Those are the reasons I chose Python - I don't have to re-invent anything. > This approach would have the advantage that since you don't directly > control the device, you don't have the need to tell LAVA that you are > finished with it. LAVA knows when the job you submited is done. Besides, > if a CI job crashes, LAVA won't stay forever waiting for being told that > a given device is done with, and doesn't need to care about handling > timeouts, and we don't need to worry about what is the right timeout to > wait for etc. > Does that make sense? Absolutely. I know that with all this added flexibility I am potentially making life difficult for us, but I think it will encourage adoption and is a nice, flexible method of doing some really powerful stuff. I am keen to mitigate the problems it creates as much as possible. I expect us to have jobs that specify a maximum runtime anyway (this is standard practice with lots of grid compute and cluster products). We should have a reasonably short default timeout for jobs that don't specify one to "train" users to do this right. That avoid the crashing issue to some extent. > OTOH, I realize that having the ability to reserve a device and receive > an interactive session on it is useful and would open up several other > possibilities, so I don't necessarily think it is a bad idea at all. -- James Tunnicliffe

13 years, 1 month

Linaro-android_origen-linaro builds stopped on lava dashboard Image reports

by Soumya Basak

Hi, on our linaro-android origen builds on Lava dashboard, the image report is stopped from build # 187 since March 13, 2013, https://bugs.launchpad.net/linaro-android/+bug/1173108 would you please look into the issue for our QA daily and weekly test. Best Regards Soumya Basak

13 years, 1 month

CI Runtime API

by James Tunnicliffe

Hi, Was just chatting with Tyler and he asked me to share what the API that I would like to use in the CI runtime to interact with LAVA would look like. I figure it is useful to give you guys some context, so I am going to share a simple user story. I am going to use "LAVA/CI" in the following description as a short cut for LAVA with the extra logic and dashboard we need to make this work. The most simple user story for this tool is: 1. Write CI job 2. Check into VCS 3. Tell LAVA/CI that the job exists 4. Ask LAVA/CI to run the job 5. LAVA/CI checks the job out of VCS 6. LAVA/CI start running the job[a] 7. The job requests a slave machine that matches a specification 8. The job runs a series of commands on that machine 9. The job releases the machine 10. The job completes 11. The user polls LAVA/CI to see the result of the job [a] I expect us to have a box that just sits there running these jobs (Python scripts). The scripts just run commands on other machines and shuffle files around, so 1 relatively modest computer should cope with running all the scripts at once. Now, the job could be more complex. The most likely use is that an x86 machine is requested at the start of the job and used as a build slave, then the resulting image is booted and tested on an ARM board. You may perform 1 kernel build and derive several images from it to perform single zImage testing, request one of each of your target boards and execute your boot & test on those ARM boards in parallel. We could also request an ARM server part and several other machines as traffic generators to do some multi-node testing. The nice thing is that LAVA doesn't care - it is just handing out machines. OK, so that is a bit of context out of the way. What do I actually want? First, I want to ask LAVA for a machine based on a specification I give. For now, lets stick to a name for each type (x86_64 / Panda / Origen etc). Later I think a list of keys specifying a minimum specification would be nice, such as arch=ARMv7, subarch=NEON, RAM=1GB, cpus=2. I would like to connect to it using SSH. If this is directly or by connecting to a terminal server doesn't matter. As long as I am given sufficient information to connect and log in, I don't mind if this is key based or password based. If it is inconvenient to use SSH I am happy to add code to telnet into a board. I imagine SSH is what I will use for x86 machines. I would then like to ask LAVA to boot a machine I have reserved using a particular disk image. For x86 machines, I assume this will be from a selection of VM disk images that OpenStack can boot (will need that listing). For ARM boards this will be a disk image I have published somewhere. Non-API related thought: I think it is reasonable to have an internal file server to store disk images on that we create during builds without having to push up to snapshots.linaro.org and pull them back down. It makes far more sense to boot and test an image, then optionally upload it to the wider world. Let me know if we have this soft of temporary storage available. I need to know if a machine is ready for me to use. I am happy to poll something. I need to tell LAVA/CI that I have finished with a machine. How I access that API doesn't matter to me as long as a Python library exists to allow me to interact with it without many headaches! Example code welcome :-) If you are interested, this is an example configuration that builds a kernel: http://bazaar.launchpad.net/~linaro-automation/linaro-ci-runtime/trunk/view… -- James Tunnicliffe

13 years, 1 month

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation April 2013