Messages in this thread | | | Date | Mon, 03 Nov 2014 11:33:33 +0100 | From | Daniel Lezcano <> | Subject | Re: non-Multiplatform APE6EVM broken in v3.18-rc1 |
| |
On 10/30/2014 02:34 AM, Simon Horman wrote: > On Wed, Oct 29, 2014 at 06:05:03PM +0900, Simon Horman wrote: >> On Wed, Oct 29, 2014 at 09:13:11AM +0100, Geert Uytterhoeven wrote: >>> On Wed, Oct 29, 2014 at 3:08 AM, Simon Horman <horms@verge.net.au> wrote: >>>> On Wed, Oct 29, 2014 at 09:12:58AM +0900, Simon Horman wrote: >>>>> On Tue, Oct 28, 2014 at 10:32:32AM +0100, Geert Uytterhoeven wrote: >>>>>> On Tue, Oct 28, 2014 at 10:23 AM, Simon Horman <horms@verge.net.au> wrote: >>>>>>> On Tue, Oct 28, 2014 at 08:59:28AM +0100, Geert Uytterhoeven wrote: >>>>>>>> On Tue, Oct 28, 2014 at 1:41 AM, Simon Horman <horms@verge.net.au> wrote: >>>>>>>>> I have noticed that there appears to be a regression between v3.17 and >>>>>>>>> v3.18-rc1 such that non-multiplatform APE6EVM (ape6evm_defconfig) no longer >>>>>>>>> boots. This appears to be the case using both reference DT (MACH_APE6EVM) >>> >>>> It seems that the boot stops here: >>>> >>>> ... >>>> smsc911x smsc911x eth0: MAC Address: 00:08:f7:00:02:4b >>>> rcar_thermal rcar_thermal: Runtime PM disabled, clock forced on. >>>> rcar_thermal rcar_thermal: 3 sensor probed >>>> sh_mobile_sdhi sh_mobile_sdhi.0: Runtime PM disabled, clock forced on. >>>> sh_mobile_sdhi sh_mobile_sdhi.0: No vqmmc regulator found >>>> >>>> I re-ran my bisection and this time the following showed up as the culprit. >>>> >>>> I suspect that the initialisation of mmcif, which is usually the next >>>> device to be initialised, sleeps and never wakes up because the timer is >>>> disabled. >>>> >>>> commit c387f07e6205cc13f57c1def5f885bf0a20e1c2d >>>> Author: Sudeep Holla <sudeep.holla@arm.com> >>>> Date: Mon Sep 29 01:50:05 2014 +0200 >>>> >>>> clocksource: arm_arch_timer: Discard unavailable timers correctly >>> >>> Apparently reported and fixed by Laurent and a few others, cfr. >>> http://www.spinics.net/lists/arm-kernel/msg371615.html > > I have temporarily cherry-picked the following, which is no present in > linux-next, into the devel branch of the renesas tree. It appears to > resolve the problem I reported. > > b0ad5917960ca80f96bae ("ARM/ARM64: arch-timer: fix arch_timer_probed logic")
Yes, that is the right one.
This patch is now upstream and will be in -rc3.
Thanks -- Daniel
-- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |