Greetings,
The current 13.02 schedule has been published on wiki:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule
llct rebuild is planned later today.
The 13.02 release would be v3.8-rc8 based (tentative).
Please make sure that requests to add new topics (with the git branch to
pull from) have been sent to me, or will be sent as soon as the topic is
ready. I would appreciate a "heads up" like information on the new
topics which are more complex than a couple patches on top of mainline.
For the moment I am aware of the kvm topic only. Anything else?
Thanks,
Andrey
Hi,
We have installed Ubuntu 12.04 (Precise Pangolin) 64-bit.
But unable to install svn.
rajkiran@rajkiran-OptiPlex-780:~$ sudo apt-get install subversion
Reading package lists... Error!
W: Duplicate sources.list entry cdrom://Ubuntu 12.04.1 LTS _Precise Pangolin_ - Release amd64 (20120823.1)/ precise/main i386 Packages (/var/lib/apt/lists/Ubuntu%2012.04.1%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Release%20amd64%20(20120823.1)_dists_precise_main_binary-i386_Packages)
W: Duplicate sources.list entry cdrom://Ubuntu 12.04.1 LTS _Precise Pangolin_ - Release amd64 (20120823.1)/ precise/restricted i386 Packages (/var/lib/apt/lists/Ubuntu%2012.04.1%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Release%20amd64%20(20120823.1)_dists_precise_restricted_binary-i386_Packages)
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/extras.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages
E: The package lists or status file could not be parsed or opened.
Could you please help us resolve the issue?
Regards,
Amar
________________________________
From: Dave Pigott [dave.pigott(a)linaro.org]
Sent: 19 February, 2013 4:59 PM
To: Amar Shankar
Cc: linaro-dev(a)lists.linaro.org; Prasad Raju; Rajkiran Mulugu
Subject: Re: Failure to generate beagle_sd.img using linaro-media-create
As James said, Anything from the LTS (12.04 - Precise) onwards.
Dave
On 19 Feb 2013, at 10:02, Amar Shankar <Amar.Shankar(a)infotech-enterprises.com<mailto:Amar.Shankar@infotech-enterprises.com>> wrote:
No
________________________________
DISCLAIMER:
This email may contain confidential information and is intended only for the use of the specific individual(s) to which it is addressed. If you are not the intended recipient of this email, you are hereby notified that any unauthorized use, dissemination or copying of this email or the information contained in it or attached to it is strictly prohibited. If you received this message in error, please immediately notify the sender at Infotech and delete the original message.
Linaro 13.02 Release (Calendar Week 9): Here is test result summary for
Linux Linaro ubuntu Quantal image on following boards:
1) ARM Versatile Express A9;
2) Samsung Arndale;
3) TI Panda 4430;
4) TI Panda 4460;
5) ST Ericsson Snowball.
Synopsis: Kernel version on all boards has been upgraded to "3.8.0-1"; TI
Panda 4460 booting failed.
1. ARM Versatile Express A9 + Linux Linaro Quantal (Column M):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV…
It keeps exactly same status since calendar week 50 last year: only "Halt"
& "Device Tree" test failed, all other features work well.
2. Samsung Arndale + Linux Linaro Quantal (Column G):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdGZJS…
It keeps same status as last week: system hangs during the Power Management
test, HDMI display is unavailable. All other features work well.
3. TI Panda 4430 + Linux Linaro Quantal (Column M):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
USB Host, Ethernet and Power Management back to work, WiFi, HDMI and DVI-D
are still unavailable. All other features work well.
4. TI Panda 4460 + Linux Linaro Quantal (Column M):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ…
System booting failed since last week, all test cases are blocked. No
release for this board in this monthly cycle.
5. ST Ericsson Snowball + Linux Linaro Quantal (Column M):
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFJ4X…
It keeps same status as last week: Power Management, Reboot and HDMI
display don't work, also many error logs show about SD MMC I/O. All other
features work well.
For the previous week test summary (Calendar Week 8), please refer to
attachment.
Thank you.
Best Regards
Botao Sun
Add display-timing node parsing to drm fimd and depends on
the display helper patchset at
http://lists.freedesktop.org/archives/dri-devel/2013-January/033998.html
It also adds pinctrl support for drm fimd.
changes since v7:
- addressed comments from Joonyoung Shim <jy0922.shim(a)samsung.com> to remove a unnecessary variable.
changes since v6:
addressed comments from Inki Dae <inki.dae(a)samsung.com> to
separated out the pinctrl functionality and made a separate patch.
changes since v5:
- addressed comments from Inki Dae <inki.dae(a)samsung.com>,
to remove the allocation of 'fbmode' and replaced
'-1'in "of_get_fb_videomode(dev->of_node, fbmode, -1)" with
OF_USE_NATIVE_MODE.
changes since v4:
- addressed comments from Paul Menzel
<paulepanter(a)users.sourceforge.net>, to modify the commit message
changes since v3:
- addressed comments from Sean Paul <seanpaul(a)chromium.org>, to modify
the return values and print messages.
changes since v2:
- moved 'devm_pinctrl_get_select_default' function call under
'if (pdev->dev.of_node)', this makes NON-DT code unchanged.
(reported by: Rahul Sharma <r.sh.open(a)gmail.com>)
changes since v1:
- addressed comments from Sean Paul <seanpaul(a)chromium.org>
Vikas Sajjan (2):
video: drm: exynos: Add display-timing node parsing using video
helper function
video: drm: exynos: Add pinctrl support to fimd
drivers/gpu/drm/exynos/exynos_drm_fimd.c | 34 ++++++++++++++++++++++++++----
1 file changed, 30 insertions(+), 4 deletions(-)
--
1.7.9.5
On my smp platform which is made of 5 cores in 2 clusters, I have the
nr_busy_cpu field of sched_group_power struct that is not null when the
platform is fully idle. The root cause seems to be:
During the boot sequence, some CPUs reach the idle loop and set their
NOHZ_IDLE flag while waiting for others CPUs to boot. But the nr_busy_cpus
field is initialized later with the assumption that all CPUs are in the busy
state whereas some CPUs have already set their NOHZ_IDLE flag.
During the initialization of the sched_domain, we set the NOHZ_IDLE flag when
nr_busy_cpus is initialized to 0 in order to have a coherent configuration.
If a CPU enters idle and call set_cpu_sd_state_idle during the build of the
new sched_domain it will not corrupt the initial state
set_cpu_sd_state_busy is modified and clears the NOHZ_IDLE only if a non NULL
sched_domain is attached to the CPU (which is the case during the rebuild)
Change since V3;
- NOHZ flag is not cleared if a NULL domain is attached to the CPU
- Remove patch 2/2 which becomes useless with latest modifications
Change since V2:
- change the initialization to idle state instead of busy state so a CPU that
enters idle during the build of the sched_domain will not corrupt the
initialization state
Change since V1:
- remove the patch for SCHED softirq on an idle core use case as it was
a side effect of the other use cases.
Signed-off-by: Vincent Guittot <vincent.guittot(a)linaro.org>
---
kernel/sched/core.c | 4 +++-
kernel/sched/fair.c | 9 +++++++--
2 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 26058d0..c730a4e 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5884,7 +5884,9 @@ static void init_sched_groups_power(int cpu, struct sched_domain *sd)
return;
update_group_power(sd, cpu);
- atomic_set(&sg->sgp->nr_busy_cpus, sg->group_weight);
+ atomic_set(&sg->sgp->nr_busy_cpus, 0);
+ set_bit(NOHZ_IDLE, nohz_flags(cpu));
+
}
int __weak arch_sd_sibling_asym_packing(void)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 81fa536..2701a92 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -5403,15 +5403,20 @@ static inline void set_cpu_sd_state_busy(void)
{
struct sched_domain *sd;
int cpu = smp_processor_id();
+ int clear = 0;
if (!test_bit(NOHZ_IDLE, nohz_flags(cpu)))
return;
- clear_bit(NOHZ_IDLE, nohz_flags(cpu));
rcu_read_lock();
- for_each_domain(cpu, sd)
+ for_each_domain(cpu, sd) {
atomic_inc(&sd->groups->sgp->nr_busy_cpus);
+ clear = 1;
+ }
rcu_read_unlock();
+
+ if (likely(clear))
+ clear_bit(NOHZ_IDLE, nohz_flags(cpu));
}
void set_cpu_sd_state_idle(void)
--
1.7.9.5
Frederic,
Here is a first pass at some changes needed in order to add ARM
support.
I have another series coming that instruments the syscalls, exceptions
etc. on ARM also, but this one is just to get some prerequisites out
for broader discussion.
This series applies on top of your 3.8-rc6-nohz4 branch, and is also available
here:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux.git wip/arm-nohz/prereq
I'm aware of the >80 column warnings from checkpatch on the atomic64
conversion patch, but wanted to get some feedback on this approach
before fixing all those up. Maybe some simpler wrappers in
kernel_stat.h would make this a bit cleaner?
Kevin
Kevin Hilman (5):
context tracking: conditionalize guest support based on CONFIG_KVM
kernel_cpustat: convert to atomic 64-bit accessors
virt CPU accounting: Kconfig: drop 64-bit requirment
cputime: use do_div() for nsec resolution conversion helpers
ARM: Kconfig: allow virt CPU accounting
arch/arm/Kconfig | 1 +
fs/proc/stat.c | 36 +++++++++++++-------------
fs/proc/uptime.c | 2 +-
include/asm-generic/cputime_nsecs.h | 51 +++++++++++++++++++++++++++----------
include/linux/kernel_stat.h | 2 +-
init/Kconfig | 2 +-
kernel/context_tracking.c | 4 +++
kernel/sched/core.c | 10 ++++----
kernel/sched/cputime.c | 24 ++++++++---------
9 files changed, 80 insertions(+), 52 deletions(-)
--
1.8.1.2
Hi,
Release test report (week-9) 13.02: Here is test result summary for
big.LITTLE MP Scheduler test on TC2 platform with Android image
sched_tests.git No of Test Cases Tests Run Tests Pass Tests Fail Absolute
pass rate (%) Failure Analysis/Comments
Regression 20 19 19 0 100 -
mpbasicsuite 10 9 9 1 90 -
mpcoresuite 4 4 4 0 75 -
mpextendedsuite 6 6 4 2 66.7 -
mploadbalance 2 2 2 0 100 -
Android Build:
https://android-build.linaro.org/builds/~linaro-android/vexpress-linaro-mp-…
Linux kernel:
Linux version 3.8.0-00928-g7d866cd (jenkins-build@ip-10-10-66-148
) (gcc version 4.7.3 20130205 (prerelease) (Linaro GCC 4.7-2013.02) ) #1 SMP Sat
Feb 23 11:31:29 UTC 2013
Results spread sheet:
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0Ai9ggMs8bsGJdER3a…
summary:
No regression or new bugs found in this test cycle.
Results are same as week-8.
Best regards
Naresh Kamboju
Guenter,
Please check this v3 patches, thanks.
Anton Vorontsov and David Woodhouse,
Please have a look at this 1/3 and 2/3 patches, thanks.
v2 -> v3 changes:
- Add interface for converting voltage to temperature
- Remove temp5 sensor since we cannot offer temperature read interface of it
- Update hyst to use absolute temperature instead of a difference
- Add the 3/3 patch
v1 -> v2 changes:
- Add Documentation/hwmon/abx500 and Documentation/hwmon/abx500
- Make devices which cannot report milli-Celsius invisible
- Add temp5_crit interface
- Re-work the old find_active_thresholds() to threshold_updated()
- Reset updated_min_alarm and updated_max_alarm at the end of each loop
- Update the hyst mechamisn to make it works as real hyst
- Remove non-stand attributes
- Re-order the operations sequence inside probe and remove functions
- Update all the lock usages to eliminate race conditions
- Make attibutes index starts from 0
also changes:
- Since the old [1/2] "ARM: ux500: rename ab8500 to abx500 for hwmon driver"
has been merged by Samuel, so won't send it again.
- Add another new patch "ab8500_btemp: export two symblols" as [2/2] of this
patch set.
Hongbo Zhang (3):
ab8500_btemp: make get_temp interface public
ab8500: make res_to_temp tables public
hwmon: add ST-Ericsson ABX500 hwmon driver
Documentation/hwmon/ab8500 | 22 ++
Documentation/hwmon/abx500 | 26 ++
drivers/hwmon/Kconfig | 13 +
drivers/hwmon/Makefile | 1 +
drivers/hwmon/ab8500.c | 178 +++++++++++++
drivers/hwmon/abx500.c | 501 +++++++++++++++++++++++++++++++++++
drivers/hwmon/abx500.h | 87 ++++++
drivers/power/ab8500_bmdata.c | 8 +-
drivers/power/ab8500_btemp.c | 2 +-
include/linux/mfd/abx500/ab8500-bm.h | 5 +
10 files changed, 840 insertions(+), 3 deletions(-)
create mode 100644 Documentation/hwmon/ab8500
create mode 100644 Documentation/hwmon/abx500
create mode 100644 drivers/hwmon/ab8500.c
create mode 100644 drivers/hwmon/abx500.c
create mode 100644 drivers/hwmon/abx500.h
--
1.8.0
Hi,
Several builds became "unstable" (in jenkins term) without changes in the jobs:
IOERROR: BUILD-INFO.txt is not present in build.
Obviously, it seems BUILD-INFO.txt is now enforced and some jobs are
still using EULA.txt mechanism.
While I don't have any issues with (en)forcing users to use
BUILD-INFO.txt, I would have expected some notifications to allow job
maintainers to adjust the builds as appropriate.
Once again, it isn't the kind of changes to deploy the release week.
Cheers,
--
Fathi Boudra
Release Manager | Developer Platform Tech Lead
Linaro.org | Open source software for ARM SoCs