linaro-kernel

linaro-kernel@lists.linaro.org

10095 discussions

[PATCH 1/2] timer: store cpu-number in 'struct tvec_base'

by Viresh Kumar

When a timer is enqueued or modified on a NO_HZ_FULL target (local or remote), the target is expected to re-evaluate its timer wheel to decide if tick must be restarted to handle timer expirations. If it doesn't re-evaluate timer wheel and restart tick, it wouldn't be able to call timer's handler on its expiration. It would be delayed until the time tick is restarted again. Currently the max delay can be 1 second as returned by scheduler_tick_max_deferment(), but it can increase in future. To handle this, currently we are calling wake_up_nohz_cpu() from add_timer_on() but what about timers enqueued/modified with other APIs? For example, in __mod_timer() we get target cpu (where the timer should get enqueued) by calling get_nohz_timer_target() and it is free to return a NO_HZ_FULL cpu as well. So, we *should* re-evaluate timer wheel there as well, otherwise call to timer's handler might be delayed as explained earlier. In order to fix this issue we can move wake_up_nohz_cpu(cpu) to internal_add_timer() so that it is well handled for any add-timer API. LKML discussion about this: https://lkml.org/lkml/2014/6/4/169 This requires internal_add_timer() to get cpu number from per-cpu object 'base', as all the callers might not have cpu number to pass to internal_add_timer(). For example, in __mod_timer() we find timer's base from 'timer' pointer and not from per-cpu arithmetic. Thus, this patch adds another field 'cpu' in 'struct tvec_base' which will store cpu number of the cpu it belongs to. Next patch will then move wake_up_nohz_cpu() to internal_add_timer(). Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- kernel/timer.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel/timer.c b/kernel/timer.c index 3bb01a3..9e5f4f2 100644 --- a/kernel/timer.c +++ b/kernel/timer.c @@ -82,6 +82,7 @@ struct tvec_base { unsigned long next_timer; unsigned long active_timers; unsigned long all_timers; + int cpu; struct tvec_root tv1; struct tvec tv2; struct tvec tv3; @@ -1568,6 +1569,7 @@ static int init_timers_cpu(int cpu) } spin_lock_init(&base->lock); tvec_base_done[cpu] = 1; + base->cpu = cpu; } else { base = per_cpu(tvec_bases, cpu); } -- 2.0.0.rc2

11 years, 1 month

Re: USB serial in ubuntu for arndale

by Botao Sun

Hi Alexandru, Here is the Linaro Kernel git repository list: https://git.linaro.org/?a=project_list;pf=kernel And which platform are you working on? Android or ubuntu? I ask because the Kernel version on Android is the old one: 3.9.1 FYI. On 5 June 2014 23:56, Alexandru Rosca <srosca(a)bu.edu> wrote: > Hi Botao, > > The instructions online for building and deploying a linux kernel seems to > be for version 3.1. I am using the latest arndale OS from the linaro > releases and would like to know which source code you suggest I compile > with the config file. > > Cheers, > Alex > > > On Thu, Jun 5, 2014 at 9:47 AM, Botao Sun <botao.sun(a)linaro.org> wrote: > >> + Linaro Kernel and Samsung Landing Team >> >> Hi Alexandru, >> >> As I know for the Linux mainline Kernel, we can run make menuconfig then >> search the keyword by typing "/" and USB_SERIAL. >> >> Since we already have Linaro Samsung Arndale Kernel config file, then it >> would be better to use this file and modify USB_SERIAL related items later: >> >> https://www.kernel.org/doc/index-old.html#Using_an_existing_configuration >> >> FYI. >> >> Thanks. >> >> >> Best Regards >> Botao Sun >> >> >> On 5 June 2014 07:11, Alexandru Rosca <srosca(a)bu.edu> wrote: >> >>> Dear Botao Sun, >>> >>> I have an arndale board for which I would like to communicate with >>> serially via an FTDI and some microcontrollers. It seems that the linaro >>> kernel does not support this. I was thinking of compiling a kernel with the >>> USB SERIAL config option set. Could you advise me on how to do this? Can I >>> just use the config file for the arndale and modify it for compilation? >>> >>> Thank you, >>> Sasha >>> >> >> >

11 years, 1 month

Re: USB serial in ubuntu for arndale

by Botao Sun

+ Linaro Kernel and Samsung Landing Team Hi Alexandru, As I know for the Linux mainline Kernel, we can run make menuconfig then search the keyword by typing "/" and USB_SERIAL. Since we already have Linaro Samsung Arndale Kernel config file, then it would be better to use this file and modify USB_SERIAL related items later: https://www.kernel.org/doc/index-old.html#Using_an_existing_configuration FYI. Thanks. Best Regards Botao Sun On 5 June 2014 07:11, Alexandru Rosca <srosca(a)bu.edu> wrote: > Dear Botao Sun, > > I have an arndale board for which I would like to communicate with > serially via an FTDI and some microcontrollers. It seems that the linaro > kernel does not support this. I was thinking of compiling a kernel with the > USB SERIAL config option set. Could you advise me on how to do this? Can I > just use the config file for the arndale and modify it for compilation? > > Thank you, > Sasha >

11 years, 1 month

[PATCH 1/3] arm64: Enable OPP

by Mark Brown

From: Mark Brown <broonie(a)linaro.org> Some of the generic drivers used on ARM class systems use OPP so allow it to be selected in Kconfig. No code is required for this, it is not clear to me why there is config for this option. Signed-off-by: Mark Brown <broonie(a)linaro.org> --- arch/arm64/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index 8ccdd2646ae3..8256d6d09d33 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -2,6 +2,7 @@ config ARM64 def_bool y select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_USE_CMPXCHG_LOCKREF + select ARCH_HAS_OPP select ARCH_HAS_SG_CHAIN select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST select ARCH_WANT_OPTIONAL_GPIOLIB -- 2.0.0.rc2

11 years, 1 month

[PATCH v2 0/6] sched: expel confusing usage of the term "power"

by Nicolas Pitre

"Power" is a very bad term in the scheduler context. There are so many meanings that can be attached to it. And with the upcoming "power aware" scheduler work, confusion is sure to happen. The definition of "power" is typically the rate at which work is performed, energy is converted or electric energy is transferred. The notion of "compute capacity" is rather at odds with "power" to the point many comments in the code have to make it explicit that "capacity" is the actual intended meaning. So let's make it clear what we man by using "capacity" in place of "power" directly in the code. That will make the introduction of actual "power consumption" concepts much clearer later on. This is based on the latest tip tree to apply correctly on top of existing scheduler changes already queued there. Changes from v1: - capa_factor and SCHED_CAPA_* changed to be spelled "capacity" in full to save peterz some Chupacabra nightmares - some minor corrections in commit logs - rebased on latest tip tree arch/arm/kernel/topology.c | 54 +++---- include/linux/sched.h | 8 +- kernel/sched/core.c | 87 ++++++----- kernel/sched/fair.c | 323 ++++++++++++++++++++------------------- kernel/sched/sched.h | 18 +-- 5 files changed, 246 insertions(+), 244 deletions(-)

11 years, 1 month

[PATCH 3.4 049/214] hrtimer: Set expiry time before switch_hrtimer_base()

by Greg Kroah-Hartman

3.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Viresh Kumar <viresh.kumar(a)linaro.org> commit 84ea7fe37908254c3bd90910921f6e1045c1747a upstream. switch_hrtimer_base() calls hrtimer_check_target() which ensures that we do not migrate a timer to a remote cpu if the timer expires before the current programmed expiry time on that remote cpu. But __hrtimer_start_range_ns() calls switch_hrtimer_base() before the new expiry time is set. So the sanity check in hrtimer_check_target() is operating on stale or even uninitialized data. Update expiry time before calling switch_hrtimer_base(). [ tglx: Rewrote changelog once again ] Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> Cc: linaro-kernel(a)lists.linaro.org Cc: linaro-networking(a)linaro.org Cc: fweisbec(a)gmail.com Cc: arvind.chauhan(a)arm.com Link: http://lkml.kernel.org/r/81999e148745fc51bbcd0615823fbab9b2e87e23.139988225… Signed-off-by: Thomas Gleixner <tglx(a)linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> --- kernel/hrtimer.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) --- a/kernel/hrtimer.c +++ b/kernel/hrtimer.c @@ -985,11 +985,8 @@ int __hrtimer_start_range_ns(struct hrti /* Remove an active timer from the queue: */ ret = remove_hrtimer(timer, base); - /* Switch the timer base, if necessary: */ - new_base = switch_hrtimer_base(timer, base, mode & HRTIMER_MODE_PINNED); - if (mode & HRTIMER_MODE_REL) { - tim = ktime_add_safe(tim, new_base->get_time()); + tim = ktime_add_safe(tim, base->get_time()); /* * CONFIG_TIME_LOW_RES is a temporary way for architectures * to signal that they simply return xtime in @@ -1004,6 +1001,9 @@ int __hrtimer_start_range_ns(struct hrti hrtimer_set_expires_range_ns(timer, tim, delta_ns); + /* Switch the timer base, if necessary: */ + new_base = switch_hrtimer_base(timer, base, mode & HRTIMER_MODE_PINNED); + timer_stats_hrtimer_set_start_info(timer); leftmost = enqueue_hrtimer(timer, new_base);

11 years, 1 month

mainline boot: 61 pass, 2 fail (v3.15-rc8-6406-g00170fd)

by Kevin's boot bot

Tree/Branch: mainline Git describe: v3.15-rc8-6406-g00170fd Failed boot tests (console logs at the end) =========================================== ste-snowball: FAIL: arm-multi_v7_defconfig ste-snowball: FAIL: arm-u8500_defconfig Full Report =========== arm-davinci_all_defconfig ------------------------- legacy,dm365evm 0 min 17.6 sec: PASS da850-evm 0 min 15.4 sec: PASS arm-tegra_defconfig ------------------- tegra124-jetson-tk1 0 min 17.3 sec: PASS tegra30-beaver 0 min 17.4 sec: PASS arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y ---------------------------------------- tegra124-jetson-tk1 0 min 17.4 sec: PASS armada-xp-openblocks-ax3-4 0 min 23.9 sec: PASS omap5-uevm 1 min 42.1 sec: PASS (Warnings: 6) sun7i-a20-cubieboard2 0 min 12.9 sec: PASS arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y ---------------------------------------------- armada-xp-openblocks-ax3-4 0 min 23.6 sec: PASS armada-370-mirabox 0 min 21.7 sec: PASS arm-omap2plus_defconfig ----------------------- legacy,3730xm 0 min 36.1 sec: PASS am335x-boneblack 0 min 22.5 sec: PASS omap3-beagle-xm 0 min 48.2 sec: PASS legacy,3530beagle 0 min 22.8 sec: PASS (Warnings: 1) omap4-panda 0 min 48.8 sec: PASS omap3-overo-tobi 0 min 23.4 sec: PASS am335x-bone 0 min 24.1 sec: PASS omap3-overo-storm-tobi 0 min 22.2 sec: PASS omap5-uevm 0 min 56.2 sec: PASS (Warnings: 6) omap3-n900 0 min 17.7 sec: PASS legacy,n900 0 min 17.5 sec: PASS (Warnings: 1) omap4-panda-es 0 min 52.5 sec: PASS legacy,3730storm 0 min 20.3 sec: PASS legacy,3530overo 0 min 21.3 sec: PASS (Warnings: 1) arm-multi_v7_defconfig ---------------------- imx6dl-wandboard,wand-solo 0 min 15.4 sec: PASS am335x-boneblack 0 min 22.0 sec: PASS sun7i-a20-cubieboard2 0 min 12.8 sec: PASS sun4i-a10-cubieboard 0 min 17.5 sec: PASS exynos5410-smdk5410 0 min 28.9 sec: PASS am335x-bone 0 min 23.6 sec: PASS tegra124-jetson-tk1 0 min 17.9 sec: PASS armada-370-mirabox 0 min 21.7 sec: PASS omap4-panda 0 min 50.1 sec: PASS imx6q-wandboard 0 min 14.0 sec: PASS imx6dl-wandboard,wand-dual 0 min 15.4 sec: PASS ste-snowball 1 min 11.5 sec: FAIL tegra30-beaver 0 min 19.4 sec: PASS omap3-n900 0 min 16.3 sec: PASS qcom-apq8074-dragonboard 0 min 20.2 sec: PASS bcm28155-ap 0 min 27.2 sec: PASS omap3-overo-tobi 0 min 22.3 sec: PASS omap3-overo-storm-tobi 0 min 24.5 sec: PASS omap3-beagle-xm 0 min 47.8 sec: PASS exynos5420-arndale-octa 0 min 40.9 sec: PASS armada-xp-openblocks-ax3-4 0 min 25.0 sec: PASS omap5-uevm 1 min 38.8 sec: PASS (Warnings: 6) omap4-panda-es 0 min 49.2 sec: PASS exynos5250-arndale 0 min 31.1 sec: PASS arm-sunxi_defconfig ------------------- sun7i-a20-cubieboard2 0 min 11.6 sec: PASS sun4i-a10-cubieboard 0 min 16.6 sec: PASS arm-bcm_defconfig ----------------- bcm28155-ap 0 min 23.5 sec: PASS arm-exynos_defconfig -------------------- exynos5420-arndale-octa 0 min 39.7 sec: PASS exynos5250-arndale 0 min 30.2 sec: PASS exynos5410-smdk5410 0 min 27.4 sec: PASS arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual 0 min 15.8 sec: PASS imx6dl-wandboard,wand-solo 0 min 15.8 sec: PASS imx6q-wandboard 0 min 14.2 sec: PASS arm-u8500_defconfig ------------------- ste-snowball 1 min 53.1 sec: FAIL arm-multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y ---------------------------------------------- armada-xp-openblocks-ax3-4 0 min 26.7 sec: PASS armada-370-mirabox 0 min 22.3 sec: PASS arm-mvebu_v7_defconfig ---------------------- armada-xp-openblocks-ax3-4 0 min 22.3 sec: PASS armada-370-mirabox 0 min 20.1 sec: PASS arm-sama5_defconfig ------------------- sama5d35ek 0 min 15.3 sec: PASS Console logs for failures ========================= arm-multi_v7_defconfig ---------------------- ste-snowball: FAIL: last 40 lines of boot log: ---------------------------------------------- [ 48.608703] List of all partitions: [ 48.612243] b300 7634944 mmcblk0 driver: mmcblk [ 48.617614] b301 3968 mmcblk0p1 00000000-01 [ 48.622955] b302 53248 mmcblk0p2 00000000-02 [ 48.628295] b303 454656 mmcblk0p3 00000000-03 [ 48.633636] b330 128 mmcblk0rpmb (driver?) [ 48.638854] b320 2048 mmcblk0boot1 (driver?) [ 48.644165] b310 2048 mmcblk0boot0 (driver?) [ 48.649475] No filesystem could mount root, tried: ext4 [ 48.654815] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,3) [ 48.663238] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.15.0-rc8-06406-g00170fd #1 [ 48.670837] [<c0215934>] (unwind_backtrace) from [<c0211570>] (show_stack+0x10/0x14) [ 48.678588] [<c0211570>] (show_stack) from [<c07f6674>] (dump_stack+0x78/0x94) [ 48.685821] [<c07f6674>] (dump_stack) from [<c07f4148>] (panic+0x90/0x208) [ 48.692687] [<c07f4148>] (panic) from [<c0ac10d4>] (mount_block_root+0x1f4/0x230) [ 48.700164] [<c0ac10d4>] (mount_block_root) from [<c0ac1204>] (mount_root+0xf4/0x114) [ 48.707977] [<c0ac1204>] (mount_root) from [<c0ac1350>] (prepare_namespace+0x12c/0x190) [ 48.716003] [<c0ac1350>] (prepare_namespace) from [<c0ac0d00>] (kernel_init_freeable+0x184/0x1cc) [ 48.724884] [<c0ac0d00>] (kernel_init_freeable) from [<c07f1d7c>] (kernel_init+0x8/0xec) [ 48.732971] [<c07f1d7c>] (kernel_init) from [<c020e8f8>] (ret_from_fork+0x14/0x3c) [ 48.740539] CPU0: stopping [ 48.743225] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.15.0-rc8-06406-g00170fd #1 [ 48.750793] [<c0215934>] (unwind_backtrace) from [<c0211570>] (show_stack+0x10/0x14) [ 48.758544] [<c0211570>] (show_stack) from [<c07f6674>] (dump_stack+0x78/0x94) [ 48.765777] [<c07f6674>] (dump_stack) from [<c02141bc>] (handle_IPI+0x138/0x174) [ 48.773162] [<c02141bc>] (handle_IPI) from [<c0208898>] (gic_handle_irq+0x64/0x6c) [ 48.780731] [<c0208898>] (gic_handle_irq) from [<c0212080>] (__irq_svc+0x40/0x50) [ 48.788208] Exception stack(0xc0b63f58 to 0xc0b63fa0) [ 48.793243] 3f40: ffffffed 00000000 [ 48.801422] 3f60: ffffffed c021ea00 c0b62000 c0b6a4c4 c0b6a458 00000000 00000000 00000000 [ 48.809570] 3f80: c0b5fda0 c0b62000 00000000 c0b63fa0 c020f438 c020f43c 60000013 ffffffff [ 48.817749] [<c0212080>] (__irq_svc) from [<c020f43c>] (arch_cpu_idle+0x30/0x3c) [ 48.825164] [<c020f43c>] (arch_cpu_idle) from [<c027afb8>] (cpu_startup_entry+0x1d4/0x214) [ 48.833404] [<c027afb8>] (cpu_startup_entry) from [<c0ac0b20>] (start_kernel+0x2e8/0x344) [ 48.841583] [<c0ac0b20>] (start_kernel) from [<00208074>] (0x208074) [ 48.847930] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,3) ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: Kernel panic # PYBOOT: Time: 71.46 seconds. # PYBOOT: Result: FAIL arm-u8500_defconfig ------------------- ste-snowball: FAIL: last 40 lines of boot log: ---------------------------------------------- [ 3.412078] platform musb-hdrc.20.auto: Driver musb-hdrc requests probe deferral [ 3.420013] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.20.auto [ 3.431915] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.20.auto) status -22 [ 3.439239] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.450714] musb-ux500 musb-hdrc.20.auto: Error applying setting, reverse things back [ 3.459289] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.21.auto [ 3.471221] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.21.auto) status -22 [ 3.478515] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.490020] musb-hdrc musb-hdrc.21.auto: Error applying setting, reverse things back [ 3.497833] HS USB OTG: no transceiver configured [ 3.502563] musb-hdrc musb-hdrc.21.auto: musb_init_controller failed with status -517 [ 3.510406] platform musb-hdrc.21.auto: Driver musb-hdrc requests probe deferral [ 3.518341] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.21.auto [ 3.530273] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.21.auto) status -22 [ 3.537567] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.549072] musb-ux500 musb-hdrc.21.auto: Error applying setting, reverse things back [ 3.557617] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.22.auto [ 3.569549] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.22.auto) status -22 [ 3.576843] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.588348] musb-hdrc musb-hdrc.22.auto: Error applying setting, reverse things back [ 3.596160] HS USB OTG: no transceiver configured [ 3.600891] musb-hdrc musb-hdrc.22.auto: musb_init_controller failed with status -517 [ 3.608734] platform musb-hdrc.22.auto: Driver musb-hdrc requests probe deferral [ 3.616668] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.22.auto [ 3.628601] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.22.auto) status -22 [ 3.635925] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.647399] musb-ux500 musb-hdrc.22.auto: Error applying setting, reverse things back [ 3.655914] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.23.auto [ 3.667846] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.23.auto) status -22 [ 3.675170] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.686676] musb-hdrc musb-hdrc.23.auto: Error applying setting, reverse things back [ 3.694488] HS USB OTG: no transceiver configured [ 3.699188] musb-hdrc musb-hdrc.23.auto: musb_init_controller failed with status -517 [ 3.707031] platform musb-hdrc.23.auto: Driver musb-hdrc requests probe deferral [ 3.714996] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.23.auto [ 3.726898] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.23.auto) status -22 ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 113.10 seconds. # PYBOOT: Result: FAIL

11 years, 1 month

mainline boot: 43 pass, 20 fail (v3.15-rc8-6055-gf1a7cd0)

by Kevin's boot bot

Tree/Branch: mainline Git describe: v3.15-rc8-6055-gf1a7cd0 Failed boot tests (console logs at the end) =========================================== legacy,dm365evm: FAIL: arm-davinci_all_defconfig da850-evm: FAIL: arm-davinci_all_defconfig armada-xp-openblocks-ax3-4: FAIL: arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y armada-370-mirabox: FAIL: arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y imx6dl-wandboard,wand-solo: FAIL: arm-multi_v7_defconfig am335x-boneblack: FAIL: arm-multi_v7_defconfig sun4i-a10-cubieboard: FAIL: arm-multi_v7_defconfig exynos5410-smdk5410: FAIL: arm-multi_v7_defconfig imx6q-wandboard: FAIL: arm-multi_v7_defconfig imx6dl-wandboard,wand-dual: FAIL: arm-multi_v7_defconfig ste-snowball: FAIL: arm-multi_v7_defconfig bcm28155-ap: FAIL: arm-multi_v7_defconfig omap3-beagle-xm: FAIL: arm-multi_v7_defconfig exynos5420-arndale-octa: FAIL: arm-multi_v7_defconfig omap5-uevm: FAIL: arm-multi_v7_defconfig exynos5250-arndale: FAIL: arm-multi_v7_defconfig imx6dl-wandboard,wand-dual: FAIL: arm-imx_v6_v7_defconfig imx6dl-wandboard,wand-solo: FAIL: arm-imx_v6_v7_defconfig imx6q-wandboard: FAIL: arm-imx_v6_v7_defconfig ste-snowball: FAIL: arm-u8500_defconfig Full Report =========== arm-davinci_all_defconfig ------------------------- legacy,dm365evm 0 min 0.1 sec: FAIL da850-evm 0 min 0.1 sec: FAIL arm-tegra_defconfig ------------------- tegra124-jetson-tk1 0 min 17.3 sec: PASS tegra30-beaver 0 min 34.7 sec: PASS arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y ---------------------------------------- tegra124-jetson-tk1 0 min 17.6 sec: PASS armada-xp-openblocks-ax3-4 0 min 24.4 sec: PASS omap5-uevm 1 min 38.8 sec: PASS (Warnings: 6) sun7i-a20-cubieboard2 0 min 13.5 sec: PASS arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y ---------------------------------------------- armada-xp-openblocks-ax3-4 0 min 0.2 sec: FAIL armada-370-mirabox 0 min 0.2 sec: FAIL arm-omap2plus_defconfig ----------------------- legacy,3730xm 0 min 40.3 sec: PASS am335x-boneblack 0 min 22.2 sec: PASS omap3-beagle-xm 0 min 47.2 sec: PASS legacy,3530beagle 0 min 23.4 sec: PASS (Warnings: 1) omap4-panda 0 min 49.1 sec: PASS omap3-overo-tobi 0 min 25.9 sec: PASS am335x-bone 0 min 28.9 sec: PASS omap3-overo-storm-tobi 0 min 25.0 sec: PASS omap5-uevm 0 min 59.0 sec: PASS (Warnings: 6) omap3-n900 0 min 16.6 sec: PASS legacy,n900 0 min 16.2 sec: PASS (Warnings: 1) omap4-panda-es 0 min 51.4 sec: PASS legacy,3730storm 0 min 22.4 sec: PASS legacy,3530overo 0 min 21.0 sec: PASS (Warnings: 1) arm-multi_v7_defconfig ---------------------- imx6dl-wandboard,wand-solo 0 min 0.2 sec: FAIL am335x-boneblack 0 min 0.1 sec: FAIL sun7i-a20-cubieboard2 0 min 12.8 sec: PASS sun4i-a10-cubieboard 0 min 0.2 sec: FAIL exynos5410-smdk5410 0 min 0.1 sec: FAIL am335x-bone 0 min 29.6 sec: PASS tegra124-jetson-tk1 0 min 37.7 sec: PASS armada-370-mirabox 0 min 21.8 sec: PASS omap4-panda 0 min 51.5 sec: PASS imx6q-wandboard 0 min 0.1 sec: FAIL imx6dl-wandboard,wand-dual 0 min 0.1 sec: FAIL ste-snowball 0 min 0.2 sec: FAIL tegra30-beaver 0 min 31.0 sec: PASS omap3-n900 0 min 15.4 sec: PASS qcom-apq8074-dragonboard 0 min 17.2 sec: PASS bcm28155-ap 0 min 0.1 sec: FAIL omap3-overo-tobi 0 min 31.3 sec: PASS omap3-overo-storm-tobi 0 min 21.0 sec: PASS omap3-beagle-xm 0 min 0.1 sec: FAIL exynos5420-arndale-octa 0 min 0.1 sec: FAIL armada-xp-openblocks-ax3-4 0 min 25.0 sec: PASS omap5-uevm 0 min 0.1 sec: FAIL omap4-panda-es 0 min 52.3 sec: PASS exynos5250-arndale 0 min 0.2 sec: FAIL arm-sunxi_defconfig ------------------- sun7i-a20-cubieboard2 0 min 11.4 sec: PASS sun4i-a10-cubieboard 0 min 15.7 sec: PASS arm-bcm_defconfig ----------------- bcm28155-ap 0 min 22.1 sec: PASS arm-exynos_defconfig -------------------- exynos5420-arndale-octa 0 min 40.0 sec: PASS exynos5250-arndale 0 min 34.9 sec: PASS exynos5410-smdk5410 0 min 27.0 sec: PASS arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual 0 min 0.2 sec: FAIL imx6dl-wandboard,wand-solo 0 min 0.1 sec: FAIL imx6q-wandboard 0 min 0.2 sec: FAIL arm-u8500_defconfig ------------------- ste-snowball 1 min 48.0 sec: FAIL arm-multi_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y ---------------------------------------------- armada-xp-openblocks-ax3-4 0 min 27.4 sec: PASS armada-370-mirabox 0 min 22.3 sec: PASS arm-mvebu_v7_defconfig ---------------------- armada-xp-openblocks-ax3-4 0 min 22.4 sec: PASS armada-370-mirabox 0 min 20.1 sec: PASS arm-sama5_defconfig ------------------- sama5d35ek 0 min 15.3 sec: PASS Console logs for failures ========================= arm-davinci_all_defconfig ------------------------- legacy,dm365evm: FAIL: last 40 lines of boot log: ------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL da850-evm: FAIL: last 40 lines of boot log: ------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL arm-mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y ---------------------------------------------- armada-xp-openblocks-ax3-4: FAIL: last 40 lines of boot log: ------------------------------------------------------------ Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.19 seconds. # PYBOOT: Result: FAIL armada-370-mirabox: FAIL: last 40 lines of boot log: ---------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.17 seconds. # PYBOOT: Result: FAIL arm-multi_v7_defconfig ---------------------- imx6dl-wandboard,wand-solo: FAIL: last 40 lines of boot log: ------------------------------------------------------------ Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.16 seconds. # PYBOOT: Result: FAIL am335x-boneblack: FAIL: last 40 lines of boot log: -------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL sun4i-a10-cubieboard: FAIL: last 40 lines of boot log: ------------------------------------------------------ Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.16 seconds. # PYBOOT: Result: FAIL exynos5410-smdk5410: FAIL: last 40 lines of boot log: ----------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL imx6q-wandboard: FAIL: last 40 lines of boot log: ------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL imx6dl-wandboard,wand-dual: FAIL: last 40 lines of boot log: ------------------------------------------------------------ Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL ste-snowball: FAIL: last 40 lines of boot log: ---------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.16 seconds. # PYBOOT: Result: FAIL bcm28155-ap: FAIL: last 40 lines of boot log: --------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL omap3-beagle-xm: FAIL: last 40 lines of boot log: ------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL exynos5420-arndale-octa: FAIL: last 40 lines of boot log: --------------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL omap5-uevm: FAIL: last 40 lines of boot log: -------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL exynos5250-arndale: FAIL: last 40 lines of boot log: ---------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.16 seconds. # PYBOOT: Result: FAIL arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual: FAIL: last 40 lines of boot log: ------------------------------------------------------------ Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.16 seconds. # PYBOOT: Result: FAIL imx6dl-wandboard,wand-solo: FAIL: last 40 lines of boot log: ------------------------------------------------------------ Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.15 seconds. # PYBOOT: Result: FAIL imx6q-wandboard: FAIL: last 40 lines of boot log: ------------------------------------------------- Conmux::Registry::lookup: dummy: error - ENOENT entry not found ~$off # PYBOOT: Exception: ERROR: Unable to connect to console. Giving up. # PYBOOT: Time: 0.16 seconds. # PYBOOT: Result: FAIL arm-u8500_defconfig ------------------- ste-snowball: FAIL: last 40 lines of boot log: ---------------------------------------------- [ 3.438598] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.450073] musb-ux500 musb-hdrc.20.auto: Error applying setting, reverse things back [ 3.458618] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.21.auto [ 3.470550] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.21.auto) status -22 [ 3.477874] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.489349] musb-hdrc musb-hdrc.21.auto: Error applying setting, reverse things back [ 3.497192] HS USB OTG: no transceiver configured [ 3.501892] musb-hdrc musb-hdrc.21.auto: musb_init_controller failed with status -517 [ 3.509735] platform musb-hdrc.21.auto: Driver musb-hdrc requests probe deferral [ 3.517669] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.21.auto [ 3.529602] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.21.auto) status -22 [ 3.536895] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.548400] musb-ux500 musb-hdrc.21.auto: Error applying setting, reverse things back [ 3.556915] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.22.auto [ 3.568847] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.22.auto) status -22 [ 3.576171] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.587646] musb-hdrc musb-hdrc.22.auto: Error applying setting, reverse things back [ 3.595458] HS USB OTG: no transceiver configured [ 3.600158] musb-hdrc musb-hdrc.22.auto: musb_init_controller failed with status -517 [ 3.608032] platform musb-hdrc.22.auto: Driver musb-hdrc requests probe deferral [ 3.615936] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.22.auto [ 3.627868] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.22.auto) status -22 [ 3.635192] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.646667] musb-ux500 musb-hdrc.22.auto: Error applying setting, reverse things back [ 3.655181] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.23.auto [ 3.667114] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.23.auto) status -22 [ 3.674438] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.685913] musb-hdrc musb-hdrc.23.auto: Error applying setting, reverse things back [ 3.693725] HS USB OTG: no transceiver configured [ 3.698425] musb-hdrc musb-hdrc.23.auto: musb_init_controller failed with status -517 [ 3.706298] platform musb-hdrc.23.auto: Driver musb-hdrc requests probe deferral [ 3.714202] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.23.auto [ 3.726135] pinctrl-nomadik soc:pinctrl: pin-256 (musb-hdrc.23.auto) status -22 [ 3.733459] pinctrl-nomadik soc:pinctrl: could not request pin 256 (GPIO256_AF28) from group usb_a_1 on device pinctrl-nomadik [ 3.744934] musb-ux500 musb-hdrc.23.auto: Error applying setting, reverse things back [ 3.753448] pinctrl-nomadik soc:pinctrl: pin GPIO256_AF28 already requested by a03e0000.usb_per5; cannot claim for musb-hdrc.24.auto ~$off # PYBOOT: Exception: kernel: ERROR: failed to boot: <class 'pexpect.TIMEOUT'> # PYBOOT: Time: 108.01 seconds. # PYBOOT: Result: FAIL

11 years, 1 month

[PATCH 3.10 027/103] hrtimer: Set expiry time before switch_hrtimer_base()

by Greg Kroah-Hartman

3.10-stable review patch. If anyone has any objections, please let me know. ------------------ From: Viresh Kumar <viresh.kumar(a)linaro.org> commit 84ea7fe37908254c3bd90910921f6e1045c1747a upstream. switch_hrtimer_base() calls hrtimer_check_target() which ensures that we do not migrate a timer to a remote cpu if the timer expires before the current programmed expiry time on that remote cpu. But __hrtimer_start_range_ns() calls switch_hrtimer_base() before the new expiry time is set. So the sanity check in hrtimer_check_target() is operating on stale or even uninitialized data. Update expiry time before calling switch_hrtimer_base(). [ tglx: Rewrote changelog once again ] Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> Cc: linaro-kernel(a)lists.linaro.org Cc: linaro-networking(a)linaro.org Cc: fweisbec(a)gmail.com Cc: arvind.chauhan(a)arm.com Link: http://lkml.kernel.org/r/81999e148745fc51bbcd0615823fbab9b2e87e23.139988225… Signed-off-by: Thomas Gleixner <tglx(a)linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> --- kernel/hrtimer.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) --- a/kernel/hrtimer.c +++ b/kernel/hrtimer.c @@ -999,11 +999,8 @@ int __hrtimer_start_range_ns(struct hrti /* Remove an active timer from the queue: */ ret = remove_hrtimer(timer, base); - /* Switch the timer base, if necessary: */ - new_base = switch_hrtimer_base(timer, base, mode & HRTIMER_MODE_PINNED); - if (mode & HRTIMER_MODE_REL) { - tim = ktime_add_safe(tim, new_base->get_time()); + tim = ktime_add_safe(tim, base->get_time()); /* * CONFIG_TIME_LOW_RES is a temporary way for architectures * to signal that they simply return xtime in @@ -1018,6 +1015,9 @@ int __hrtimer_start_range_ns(struct hrti hrtimer_set_expires_range_ns(timer, tim, delta_ns); + /* Switch the timer base, if necessary: */ + new_base = switch_hrtimer_base(timer, base, mode & HRTIMER_MODE_PINNED); + timer_stats_hrtimer_set_start_info(timer); leftmost = enqueue_hrtimer(timer, new_base);

11 years, 1 month

[PATCH 3.14 052/228] hrtimer: Set expiry time before switch_hrtimer_base()

by Greg Kroah-Hartman

3.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Viresh Kumar <viresh.kumar(a)linaro.org> commit 84ea7fe37908254c3bd90910921f6e1045c1747a upstream. switch_hrtimer_base() calls hrtimer_check_target() which ensures that we do not migrate a timer to a remote cpu if the timer expires before the current programmed expiry time on that remote cpu. But __hrtimer_start_range_ns() calls switch_hrtimer_base() before the new expiry time is set. So the sanity check in hrtimer_check_target() is operating on stale or even uninitialized data. Update expiry time before calling switch_hrtimer_base(). [ tglx: Rewrote changelog once again ] Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> Cc: linaro-kernel(a)lists.linaro.org Cc: linaro-networking(a)linaro.org Cc: fweisbec(a)gmail.com Cc: arvind.chauhan(a)arm.com Link: http://lkml.kernel.org/r/81999e148745fc51bbcd0615823fbab9b2e87e23.139988225… Signed-off-by: Thomas Gleixner <tglx(a)linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> --- kernel/hrtimer.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) --- a/kernel/hrtimer.c +++ b/kernel/hrtimer.c @@ -1003,11 +1003,8 @@ int __hrtimer_start_range_ns(struct hrti /* Remove an active timer from the queue: */ ret = remove_hrtimer(timer, base); - /* Switch the timer base, if necessary: */ - new_base = switch_hrtimer_base(timer, base, mode & HRTIMER_MODE_PINNED); - if (mode & HRTIMER_MODE_REL) { - tim = ktime_add_safe(tim, new_base->get_time()); + tim = ktime_add_safe(tim, base->get_time()); /* * CONFIG_TIME_LOW_RES is a temporary way for architectures * to signal that they simply return xtime in @@ -1022,6 +1019,9 @@ int __hrtimer_start_range_ns(struct hrti hrtimer_set_expires_range_ns(timer, tim, delta_ns); + /* Switch the timer base, if necessary: */ + new_base = switch_hrtimer_base(timer, base, mode & HRTIMER_MODE_PINNED); + timer_stats_hrtimer_set_start_info(timer); leftmost = enqueue_hrtimer(timer, new_base);

11 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel