Hi
LAVA is good for doing some tests but every time I use it I wonder why
it is so slow. So I looked more at problem.
Job which I started is going on pandaboard for 48 minutes already. So
far it did nothing related with tests which I want to run. Instead if
fetched some image, booted and started installing lot of Python packages...
This got me to idea - why not make *-lava variants of images which would
have all packages needed by LAVA infrastructure preinstalled? It would
take some minutes of Jenkins but less then LAVA one probably. Especially
when bigger set of jobs is to be run.
Opinions?
Hey Arnd,
So it looks like something has gone awry in the 3.5 pull with
Panda's mmc functionality. Trying to boot the current 3.5-rc tree, the
boot fails after not finding the root device. Looking at the boot log
I'm seeing:
omap_hsmmc: probe of omap_hsmmc.0 failed with error -22
With the same config on 3.4 it boots up fine. I also tried w/ the
omap2plus_defconfig and see the same behavior.
Before I start bisecting down, I just wanted to raise the issue here in
case there's a known fix.
thanks
-john
Good day all,
A new set of startup files have been released [1]. As with uboot, the
statup files reside in the boot sector on the emmc card and as such
requires the usage of riff for the update.
Instructions to update the startup files for Android can be found here [2].
This new set provides:
. support for new power management features.
. graceful reboot.
. a new flash layout.
. improvement on a lot of improvement reported on launchpad.
The new startup files are compatible with earlier release. It is highly
recommended to use them in conjunction with the forthcoming 12.05 release.
Best regards,
Mathieu.
[1].http://igloocommunity.org/download/linaro/startupfiles/latest/
[2].http://www.igloocommunity.org/support/Android_Getting_started_with_ICS#B…
http://xania.org/201205/gcc-explorer
Could we get Matt to provide a cross-compiler environment too? He's
already using gcc-linaro anyway.. ;-)
We could also host a version ourselves under a cool linaro.org hostname.
--
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs
Dear Linaro-Dev-Team,
we tried to getting started with the Freescale i.MX6Q Sabre Lite
Boardand have some errors that you have mentioned at your homepage
https://wiki.linaro.org/Boards/MX6QSabreLite:
"In case you somehow do not succeed with this procedure you will have to
use the manufacturing tool in order to reflash the SPI-NOR. In that case
please let me know and I can send you instructions how to program the
new loader with the manufacturing tool."
Please send us the instructions. Thank you.
Torben Zeleny
--
Mit freundlichen Grüßen,
With best regards,
Torben Zeleny
M. Sc. Electrical Engineering
Concept& Design Engineer
__________________________________________________________________
| |
| KEITH& KOEP GMBH DEVELOPMENT OF EMBEDDED CONTROL SYSTEMS |
| UELLENDAHLER STR. 199 PHONE +49 (202) 2525 322 |
| D-42109 WUPPERTAL FAX +49 (202) 2525 333 |
| GERMANY t.zeleny(a)keith-koep.com |
| http://www.keith-koep.com |
| |
| HRB B 7696 Amtsgericht Wuppertal |
| Geschäftsführer: Volker Keith, Dipl.-Phys.Ing. Luitger Koep |
| |
| Microsoft Gold Level Partner System Integration |
| Microsoft Gold Level Partner Independent Hardware Vendor |
|_________________________________________________________________|
As some of you know, we had a problem today which caused all android
tests to fail in LAVA. This is now fixed (basically, the version of adb
we had installed in the lab was too old), and if you need to you should
be safe to resubmit your jobs now.
Linaro insiders can see more details at
https://wiki.linaro.org/Internal/LAVA/Incidents/Reports/2012-05-24-all-andr…
(but really, it's not very exciting).
Apologies for the inconvenience.
Cheers,
mwh
I believe from experience on a local host that having a precloned tree
of for example current upstream linus on jenkins to use with
--reference could be a huge win. We can discuss this in the kernel-ci
session at connect.
--john
Hi Aneesh,
Adding linaro-dev in the loop as someone else could be also interested
I have reproduced my thermal error with a lava test so you can have a
complete log available here:
http://validation.linaro.org/lava-server/scheduler/job/18564/log_file
As a summary of the problem, the panda board turns off during some
sysbench tests because the SDRAM has exceeded its temperature limit
Regards,
Vincent
On 9 May 2012 14:43, Vincent Guittot <vincent.guittot(a)linaro.org> wrote:
> Hi Aneesh,
>
> Sorry for this late replay.
>
> I'm working with the Linaro 12.04 developer image which is quite close
> to the Linaro ubuntu one but without IHM.
> Te manifest gives me the following information about the kernel
> linux-image-3.3.1-38-linaro-lt-omap=3.3.1-38.38~lt~ci~00000000000001+1336186099~4fa4ad78
> which should be available here
> :git://git.linaro.org/landing-teams/leb/ti/kernel.git
>
> This issue occurs each time I run some sysbench tests on my panda
> board (revA1). I run several tests which are 20 seconds long and the
> issue occurs after few minutes
>
> I've check with my finger and the package is quite hot when the issue occurs
>
> Regards,
> Vincent
>
> On 7 May 2012 19:43, Aneesh V <aneesh(a)ti.com> wrote:
>> On 05/07/2012 10:38 AM, Mike Turquette wrote:
>>>
>>> On Thu, May 3, 2012 at 7:47 AM, Vincent Guittot
>>> <vincent.guittot(a)linaro.org> wrote:
>>>>
>>>> Hi Amit and Mike,
>>>>
>>>> While stressing the dual cortex-A9 of my panda board ( omap4430 ) with
>>>> the latest Linaro ubuntu developer environment, I reach the following
>>>> message
>>>>
>>>> [ 824.996978] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 837.243957] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 839.045318] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 845.168518] emif emif.1: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 901.361663] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 902.082672] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 914.329620] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 925.496124] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 930.537292] emif emif.2: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 938.823333] emif emif.1: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 947.828857] emif emif.1: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 954.312072] emif emif.1: temperature alert before registers are
>>>> calculated, not de-rating timings
>>>> [ 982.047271] emif emif.2: SDRAM temperature exceeds operating
>>>> limit.. Needs shut down!!!
>>>> [ 982.072784] Power down.
>>>>
>>>> It is something you have already faced ? could something miss in the
>>>> kernel ?
>>
>>
>> That should not happen normally. If all is well, it should happen only
>> if the temperature alert comes during a small window at bootup. Is that
>> the case with you. Which tree and branch are you using. Please send me
>> the details and I will take a look.
>>
>> br,
>> Aneesh