From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965257AbbD1KSA (ORCPT ); Tue, 28 Apr 2015 06:18:00 -0400 Received: from foss.arm.com ([217.140.101.70]:58895 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932686AbbD1KR4 (ORCPT ); Tue, 28 Apr 2015 06:17:56 -0400 Message-ID: <553F5E4F.9040300@arm.com> Date: Tue, 28 Apr 2015 11:17:51 +0100 From: Sudeep Holla User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Linus Walleij , "Rafael J. Wysocki" , Linux PM list , Thomas Gleixner CC: Sudeep Holla , Peter Zijlstra , Ingo Molnar , Linux Kernel Mailing List , ACPI Devel Maling List Subject: Re: [PATCH 16/20] sched/idle: Use explicit broadcast oneshot control function References: <2112147.0kYCHhbEJT@vostro.rjw.lan> <18575128.8R6Lp68k0Q@vostro.rjw.lan> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/04/15 11:11, Linus Walleij wrote: > On Thu, Apr 2, 2015 at 12:22 AM, Rafael J. Wysocki wrote: > >> From: Thomas Gleixner >> >> Replace the clockevents_notify() call with an explicit function call. >> >> Signed-off-by: Thomas Gleixner >> Signed-off-by: Rafael J. Wysocki > > For some reason this makes my Ux500 system arbitrarily hang, > especially during boot. Bisected down to this commit. > Since the entire changeset is removing the notifications > altogether I can't just revert it. > > Disabling CONFIG_CPU_IDLE removes the problem. > > Tried registering a stub driver (I just #if 0 all the code in > drivers/cpuidle/cpuidle-ux500.c) it still crashes. > > That makes me think something inside the cpuidle subsystem > is locking up after this, but my other idea is that the timer > may be involved in some way, like this is stressing the timer > in some new yet untested way. > > Has anyone else seen problems with this or is it only > ux500? > > I'm looking closer at it but feel a bit clueless... > Yes I am too in similar situation with my Vexpress platform. I did report with the lockdep logs[1] before v4.1-rc1. I still see the issue with v4.1-rc1. Regards, Sudeep [1] https://lkml.org/lkml/2015/4/23/329