linaro-validation May 2013

linaro-validation@lists.linaro.org

18 participants
24 discussions

by Naresh Kamboju

Hi, I have noticed a typo in below page http://lava.readthedocs.org/en/latest/index.html under "LAVA Components" sub section. - LAVA Andorid Test + LAVA Android Test same change is applicable for http://lava.readthedocs.org/en/latest/components.html Best regards Naresh Kamboju

10 years, 11 months

SD-MUX

by Dominic Lemire

Hello, I'm interested in the SD-MUX device. Could somebody point me to the latest information (status, schematics, suppliers, etc.) Regards, Dominic

10 years, 11 months

linux-next : Build and boot report

by Naresh Kamboju

Hi Milosz, linux-next builds reported all targets are successful. https://ci.linaro.org/jenkins/job/linux-next/ LAVA dashboard reported below status, http://validation.linaro.org/lava-server/dashboard/image-reports/ snowball: ------------ -> Buffer I/O error on device mmcblk0boot1, logical block 0 -> mmcblk0boot1: unable to read partition table -> failed to mount rootfs -> CRITICAL: Could not get master image booted properly -> ERROR: boot_linaro_image failed -> http://validation.linaro.org/lava-server/scheduler/job/55006/log_file panda (omap2plus): ------------------------- -> Test executed successful. -> http://validation.linaro.org/lava-server/scheduler/job/55004/log_file origen: --------- -> nothing shows up after below message. which means boot failed. -> Starting kernel ... -> <LAVA_DISPATCHER>2013-05-20 02:16:46 AM WARNING: Sending newline in case of corruption. -> ERROR: boot_linaro_image failed -> [ACTION-E] boot_linaro_image is finished with error (Failed to boot test image.) -> http://validation.linaro.org/lava-server/scheduler/job/54893/log_file vexpress: -------------- -> sudo flock /var/lock/lava-lmc.lck linaro-media-create --hwpack-force-yes --dev vexpress --image-file /linaro/images/tmp/tmp3MGayb/lava.img --binary /linaro/images/tmp/tmp3MGayb/linaro-raring-nano-lava-20130520-373.tar.gz --hwpack /linaro/images/tmp/tmp3MGayb/hwpack_linaro-vexpress_20130521-0245_b44_armhf_supported.tar.gz --image-size 3G --bootloader u_boot -> deploy_linaro_image is finished with error ([Errno 2] No such file or directory: '/tmp/tmpdaPV2n/etc/profile') http://validation.linaro.org/lava-server/scheduler/job/55008/log_file Here we need to identify and isolate the root cause of each build (root cause could be zImage/initrd/dtb/hardware pack/ rootfs / and etc). To do this do we need to reproduce on our local target boards ? Best regards Naresh Kamboju

10 years, 11 months

Lava Lab activity

by Dave Pigott

Hi all, I've spent this morning going around all the boards on v.l.o and getting them back online. In the process I've had quite a few failures, which I'm slowly working through fixing, so this is just a heads up that we will see health check failure rates for today as anomalously high. Thanks Dave

10 years, 11 months

ITS process info

by Paul Sokolovsky

Hello, ITS team is ramping up, and they already have bunch of infrastructure and services around. Over last few days, I tried to collect whatever was announced/mentioned in emails at: https://wiki.linaro.org/Platform/Infrastructure/infrastructure-knowledgebas… Actually, as you see there, they already have wiki, and lot of info is probably there. However, so far I didn't have a chance to read thru it, and anyway, that section is not intended to duplicate anything, rather, to serve as shortcuts to more relevant ITS info for LAVA maintenance engineers. -- Best Regards, Paul 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

10 years, 11 months

Re: [Linaro-validation] Build failed in Jenkins: LT-TI-working-tree-3.4_panda-es-omap4plus #250

by Dave Pigott

Hi Andy, I *think* the CI people probably need to handle this, since it's part of their test set up. Paul, Milo: Any ideas? Thanks Dave On 14 May 2013, at 01:16, Andy Green <andy.green(a)linaro.org> wrote: > Hi Dave - > > I'm supremely uninterested in these reports for the dead TI trees... do you know how can I remove my email from notifications for them? > > There are three trees in CI tests that will never get updated again afaik that keep spamming me. > > It might be an idea to link to the page where you can adjust notifications, on any notification. > > -Andy > > > -------- Original Message -------- > Subject: Build failed in Jenkins: LT-TI-working-tree-3.4_panda-es-omap4plus #250 > Date: Tue, 14 May 2013 00:14:07 +0000 (UTC) > From: ci_notify(a)linaro.org > To: scottb(a)linaro.org, andy.green(a)linaro.org, usman.ahmad(a)linaro.org, n-dechesne(a)ti.com > > See <https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus…> > > ------------------------------------------ > Started by timer > [EnvInject] - Loading node environment variables. > Building remotely on Precise-64 3exec (i-5033053c) in workspace <https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus…> > Checkout:LT-TI-working-tree-3.4_panda-es-omap4plus / <https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus…> - hudson.remoting.Channel@10a7a7:Precise-64 3exec (i-5033053c) > Using strategy: Default > Last Built Revision: Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf (origin/tilt-3.4) > Cloning the remote Git repository > Cloning repository git://git.linaro.org/landing-teams/working/ti/kernel.git > git --version > git version 1.7.9.5 > Fetching upstream changes from origin > Commencing build of Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf (origin/tilt-3.4) > Checking out Revision edb2dff2ab14d66f123d43a18b2b27cecf598cdf (origin/tilt-3.4) > [copy-to-slave] Copying 'builddeb', excluding nothing, from 'file:/var/lib/jenkins/userContent/' on the master to '<https://ci.linaro.org/jenkins/job/LT-TI-working-tree-3.4_panda-es-omap4plus…'> on 'Precise-64 3exec (i-5033053c)'. > [LT-TI-working-tree-3.4_panda-es-omap4plus] $ /bin/sh -xe /tmp/hudson2373270767559071380.sh > + rm -rf lci-build-tools > + export hwpack_type=panda > + export board_types=panda-es > + export kernel_config=omap4plus_defconfig > + export kernel_flavour=omap > + export git_web_url=http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git > + export lava_test_plan=ltp,pwrmgmt,lt_ti_lava > + export toolchain_url=http://releases.linaro.org/12.08/components/toolchain/binarie… > + bzr branch lp:linaro-ci lci-build-tools > You have not informed bzr of your Launchpad ID, and you must do this to > write to Launchpad or access private data. See "bzr help launchpad-login". > Branched 148 revisions. > + ./lci-build-tools/jenkins_kernel_build_inst > + test -z omap > + test -z '' > + rootfs_type=nano-lava > + test -z http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git > + test -z panda > + test -z '' > + submit_job=1 > + test -z ltp,pwrmgmt,lt_ti_lava > + test -z http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-a… > + wget -cq http://releases.linaro.org/12.08/components/toolchain/binaries/gcc-linaro-a… > Build step 'Execute shell' marked build as failure > >

10 years, 11 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

10 years, 11 months

Working from home

by Dave Pigott

Hi all, For those that don't know, I'm working from home today to concentrate on the final bits of getting the Lmp test suite complete. I will mostly not be on IRC, but will check for urgent messages around once an hour. Thanks Dave

10 years, 12 months

lava-dispatcher: fix for boot_linaro_image without deploy

by Kevin Hilman

Hi LAVA folks, I'm working on using LAVA to boot boards in my own board farm, and for starters, am trying to use a job without a 'deploy' step (so I can use the existing on-board u-boot, and control it via boot_cmds.) Currently, the dispatcher assumes that a 'deploy' step has happened before a 'boot_linaro_image' step, which is not needed for my case, so here's a patch to set some defaults so a deploy step is not needed: === modified file 'lava_dispatcher/device/master.py' --- lava_dispatcher/device/master.py 2013-04-30 11:45:15 +0000 +++ lava_dispatcher/device/master.py 2013-05-02 18:00:49 +0000 @@ -86,6 +86,10 @@ self.master_ip = None self.device_version = None + # These defaults are needed in case no 'deploy' step is used + self.deployment_data['boot_cmds'] = 'boot_cmds' + self.deployment_data['TESTER_PS1_PATTERN'] = '# ' + if config.pre_connect_command: self.context.run_command(config.pre_connect_command) For the curious, I've created a new "u-boot" device-type, Here's the config: # Always hard reset to enter on-board u-boot soft_boot_cmd = ~$hardreset # u-boot commands boot_cmds = version, printenv, boot, # Default is 'Uncompressing Linux', but that doesn't exist anymore upstream # The default should be probably be updated in # default-config/lava-dispatcher/device-defaults.conf image_boot_msg = Booting Linux And added some devices with that device type. Then I created a simple job to just boot my board using the u-boot commands: { "device_type": "u-boot", "actions": [ { "command": "boot_linaro_image", "parameters": { "options": [] } } ], "timeout": 20000, "job_name": "KJH dummy test" } The next step is to figure out how to use lava_test_shell on my targets (not running a linaro master image) so I can run my tests. Any pointers on how the requirements/setup for lava_test_shell on a non master-image (also not android/OE/ubuntu/fedora.) Kevin

10 years, 12 months

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

by Basil Eljuse

Hi Dave, A gentle reminder on this! I tried replacing even the linux-headers*.deb package also but with same effect. Unfortunately I am out of options in debugging this issue ): 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.

11 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation May 2013