From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lezcano Date: Mon, 03 Nov 2014 10:33:33 +0000 Subject: Re: non-Multiplatform APE6EVM broken in v3.18-rc1 Message-Id: <545759FD.1020806@linaro.org> List-Id: References: <20141028004131.GA8280@verge.net.au> <20141028092305.GA11937@verge.net.au> <20141029001258.GE20702@verge.net.au> <20141029020833.GA29787@verge.net.au> <20141029090502.GA32069@verge.net.au> <20141030013444.GI22052@verge.net.au> In-Reply-To: <20141030013444.GI22052@verge.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: Simon Horman , Geert Uytterhoeven Cc: Linux-sh list , Sudeep Holla , "linux-kernel@vger.kernel.org" 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 wrot= e: >>>> 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 = 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 = wrote: >>>>>>>>> I have noticed that there appears to be a regression between v3.1= 7 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 cul= prit. >>>> >>>> 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 >>>> 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 logi= c") Yes, that is the right one. This patch is now upstream and will be in -rc3. Thanks -- Daniel --=20 Linaro.org =E2=94=82 Open source software for AR= M SoCs Follow Linaro: Facebook | Twitter | Blog