Calendar Week 39: Here is test result summary for Linaro ubuntu 12.09
Release on following boards:
1) ARM Versatile Express A9;
2) Samsung Origen;
3) TI Panda Board 4430;
4) TI Panda Board 4460.
*Synopsis: "DEADLOCK" error has disappeared during boot process, except on
TI Panda platform, although it won't affect system running. Both 480p &
1080p videos can be played on Panda board with an extra package installed -
"ubuntu-omap4-extras-multimedia". Device Tree feature is still unavailable
on vexpress A9. WiFi, Bluetooth and video playback are unavailable on
Samsung Origen.*
1. vexpress A9 + ubuntu (Column AB):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV…
Device Tree blob files have recovered, although this feature is still
unavailable due to a UEFI defect, which Ryan is working on that. 480p video
playback still doesn't work on this release image. YouTube HTML5 video now
can be played, although the frame rate is low, which is as expected. All
other features remain the same as last week.
2. Origen + ubuntu (Column W):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEowN…
"DEADLOCK" error has gone on this image, and kernel version has been
upgraded to 3.6.0-1. All other features remain the same as last week.
3. Panda 4430 + ubuntu (Column Y):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
YouTube HTML5 video now can be played well, but due to Audio over HDMI
failure, no sound can be heard. Although file transfer via Bluetooth is
still unavailable, Bluetooth headset works well. 480p video on SD card can
be played well if package "ubuntu-omap4-extras-multimedia" be installed in
advance. 1080p video can be played with a low frame rate. All power
management test has passed (or skipped properly) on this image. No
significant change on all the other features.
4. Panda 4460 + ubuntu (Column X):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
Bluetooth headset doesn't work here, it hangs the board during the pair
process. Hardware acceleration works well. 3.5mm Audio input is still
unavailable and suspend / resume test failed as well. No change on all the
other features compare with last week test.
For the previous week (Calendar week 38) summary, please refer to
attachment.
Thank you.
Best Regards
Botao Sun
Hi there,
Is there any sensible comparison document for gcc vs rvct in terms of speed, code size, feature set? Is there any reason / use case to recommend rvct over gcc for non-Linux s/w?
Thx
nicolas
Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 12.654.784
Greetings,
The linux-linaro-core-tracking (llct) tree has been moved to v3.6-rc5 base.
All the topics existed in the 12.08 version of llct have been carried
over into the updated tree with few easy to resolve conflicts. The only
one which needs attention is due to commit "ASoC: Samsung: Fix build
error" [1]. In fact I had to revert it because it doesn't work with the
multiplatform topic (the latter renames all the
arch/arm/mach-<name>/include/mach dirs to
arch/arm/mach-<name>/include/mach-<name>). Sachin or Tushar, could you
take a look please?
Also the big-LITTLE-MP topic has been updated to v3.6-rc5 based
big-LITTLE-MP-v8.
The current list of the llct topics can be found in [2].
12.09 will most probably be v3.6-rc6 based. But for the moment I've
tried rebasing the linux-linaro (ll) tree to the current v3.6-rc5 based
llct, and encountered no merge issues. The current list of the ll topics
can be found in [3]. The plan is to have single topic from the ARM LT
(like the Samsung LT code is represented now) this month vs several
one-per-feature topics.
In 12.08 the linux-linaro-tracking (llt) tree was v3.4 based, and had
recent code from TI LT plus the older code (no changes for couple
months) from ARM and Samsung LTs. Any changes here in 12.09? (Are we on
v3.4 still, are there other LTs to add to this tree?).
And yes, this month llc-3.4 "core stable" tree will be introduced (first
of all, to get the Gator updates for v3.4, and some critical fixes), and
llt will start using it as a base. No more details atm,
should have something in git by the end of this week.
Please let me know if there are any updates to the existing topics, or
new topics missing. And if there are obsoleted topics. The linux-linaro
and linux-linaro-tracking trees will be frozen (only bug fixes would be
accepted afterwards, no new additions) by the end of September 18.
Thanks,
Andrey
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h…
[2]
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=blob;f=ma…
[3]
http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git;a=blob;f=ma…
In order to save power, it would be useful to schedule work onto non-IDLE cpus
instead of waking up an IDLE one.
To achieve this, we need scheduler to guide kernel frameworks (like: timers &
workqueues) on which is the most preferred CPU that must be used for these
tasks.
This patchset is about implementing this concept.
The first patch adds sched_select_cpu() routine which returns the preferred cpu
which is non-idle. It accepts max level of sched domain, upto which we can
choose a CPU from. It can accept following options: SD_SIBLING, SD_MC, SD_BOOK,
SD_CPU or SD_NUMA.
Second and Third patch are about adapting this change in workqueue framework.
Earlier discussions over this concept were done at last LPC:
http://summit.linuxplumbersconf.org/lpc-2012/meeting/90/lpc2012-sched-timer…
Figures:
--------
Test case 1:
- Performed on TC2 with ubuntu-devel
- Boot TC2 and run
$ trace-cmd record -e workqueue_execute_start
This will trace only the points, where the work actually runs.
Do, this for 150 seconds.
Results:
---------
Domain 0: CPU 0-1
Domain 1: CPU 2-4
Base Kernel: Without my modifications:
-------------------------------------
CPU No. of works run by CPU
----- -----------------------
CPU0: 7
CPU1: 445
CPU2: 444
CPU3: 315
CPU4: 226
With my modifications:
----------------------
CPU No. of works run by CPU
---- -----------------------
CPU0: 31
CPU2: 797
CPU3: 274
CPU4: 86
Test case 2:
-----------
I have created a small module, which does following:
- Create one work for each CPU (using queue_work_on(), so must schedule on that
cpu)
- Above work, will queue "n" works for each cpu with queue_work(). These works
are tracked within the module and results are printed at the end.
This gave similar results, with n ranging from 10 to 1000.
Viresh Kumar (3):
sched: Create sched_select_cpu() to give preferred CPU for power
saving
workqueue: create __flush_delayed_work to avoid duplicating code
workqueue: Schedule work on non-idle cpu instead of current one
arch/arm/Kconfig | 11 +++++++
include/linux/sched.h | 11 +++++++
kernel/sched/core.c | 88 +++++++++++++++++++++++++++++++++++++++------------
kernel/workqueue.c | 36 ++++++++++++++-------
4 files changed, 115 insertions(+), 31 deletions(-)
--
1.7.12.rc2.18.g61b472e
Hi all,
I Thought I'd let you know that we now have 5 more ST-Ericsson Snowball V11 PDKs in LAVA. They went live yesterday afternoon. In total we now have 10 snowballs but only 8 are available because one of them has been sidelined for staging, and another is not playing ball. I'm working on trying to understand if the board is just dead, or if there there is some other issue. At the moment it's not talking to the outside world at all. I'll keep you posted.
Thanks
Dave
Dave Pigott
Validation Engineer
T: +44 1223 40 00 63 | M +44 7940 45 93 44
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Hi All,
I notice that there are still some jobs being submitted to LAVA with the device-type "vexpress". This device type is now deprecated and has been replaced by the more specific device type vexpress-a9. The jobs seem to be coming from CI and Android. Could someone amend these submissions?
Thanks
Dave
Dave Pigott
Validation Engineer
T: +44 1223 40 00 63 | M +44 7940 45 93 44
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
This weekend a test rebuild of quantal quetzal did start for the amd64, i386 and
armhf architectures. The test rebuild is now finished for the main and
restricted components, and continues with the universe and multiverse components.
Results can be seen at
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201209…
The archive for the test rebuild is
https://launchpad.net/ubuntu/+archive/test-rebuild-20120922
Please help fixing the build failures for the final release.
Note that an upload won't show up in the superseded sections, if it is uploaded
to quantal-proposed, but didn't propagate yet to quantal.
Matthias
