From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: non-Multiplatform APE6EVM broken in v3.18-rc1
Date: Wed, 29 Oct 2014 09:05:03 +0000 [thread overview]
Message-ID: <20141029090502.GA32069@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWkP=t2WL64X8vKdOPXW_ZpbibXQ66un8GfVTWoc-o+tw@mail.gmail.com>
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
Great!
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: non-Multiplatform APE6EVM broken in v3.18-rc1
Date: Wed, 29 Oct 2014 18:05:03 +0900 [thread overview]
Message-ID: <20141029090502.GA32069@verge.net.au> (raw)
In-Reply-To: <CAMuHMdWkP=t2WL64X8vKdOPXW_ZpbibXQ66un8GfVTWoc-o+tw@mail.gmail.com>
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
Great!
next prev parent reply other threads:[~2014-10-29 9:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 0:41 non-Multiplatform APE6EVM broken in v3.18-rc1 Simon Horman
2014-10-28 7:59 ` Geert Uytterhoeven
2014-10-28 9:23 ` Simon Horman
2014-10-28 9:32 ` Geert Uytterhoeven
2014-10-29 0:12 ` Simon Horman
2014-10-29 2:08 ` Simon Horman
2014-10-29 2:08 ` Simon Horman
2014-10-29 8:13 ` Geert Uytterhoeven
2014-10-29 8:13 ` Geert Uytterhoeven
2014-10-29 9:05 ` Simon Horman [this message]
2014-10-29 9:05 ` Simon Horman
2014-10-30 1:34 ` Simon Horman
2014-10-30 1:34 ` Simon Horman
2014-11-03 10:33 ` Daniel Lezcano
2014-11-03 10:33 ` Daniel Lezcano
2014-11-04 0:52 ` Simon Horman
2014-11-04 0:52 ` Simon Horman
2014-10-29 21:31 ` Geert Uytterhoeven
2014-10-29 23:54 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141029090502.GA32069@verge.net.au \
--to=horms@verge.net.au \
--cc=daniel.lezcano@linaro.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.