lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 29 Oct 2014 18:05:03 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Linux-sh list <linux-sh@...r.kernel.org>,
	Sudeep Holla <sudeep.holla@....com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: non-Multiplatform APE6EVM broken in v3.18-rc1

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@...ge.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@...ge.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@...ge.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@....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!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists