From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753388AbdHWHBb (ORCPT <rfc822;w@1wt.eu>);
        Wed, 23 Aug 2017 03:01:31 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:59386 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753238AbdHWHBa (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 23 Aug 2017 03:01:30 -0400
Date: Wed, 23 Aug 2017 09:01:04 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: jeffy <jeffy.chen@rock-chips.com>
cc: Nicholas Piggin <npiggin@gmail.com>, akpm@linux-foundation.org,
        John Stultz <john.stultz@linaro.org>,
        Stephen Boyd <sboyd@codeaurora.org>, Jonathan.Cameron@huawei.com,
        paulmck@linux.vnet.ibm.com, mpe@ellerman.id.au, dzickus@redhat.com,
        sfr@canb.auug.org.au, linuxarm@huawei.com, abdhalee@linux.vnet.ibm.com,
        linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [v2] timers: Fix excessive granularity of new timers after a
 nohz idle
In-Reply-To: <599CF4C4.2070703@rock-chips.com>
Message-ID: <alpine.DEB.2.20.1708230900280.1821@nanos>
References: <20170822084348.21436-1-npiggin@gmail.com> <599CF4C4.2070703@rock-chips.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 23 Aug 2017, jeffy wrote:

> Hi guys,
> 
> I was testing a arm64 based device(chromebook bob), and the kernel hang a
> lot(during booting or suspending) on for-next(next-20170822) with this commit:
> 71acb768f5b3 (timers: Fix excessive granularity of new timers after a nohz
> idle)
> 
> After revert it(or just add "!base->is_idle" check back), things work well...

Can you please test V2?

Thanks,

	tglx