From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753313AbdHWDfj (ORCPT ); Tue, 22 Aug 2017 23:35:39 -0400 Received: from ozlabs.org ([103.22.144.67]:52125 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753142AbdHWDfi (ORCPT ); Tue, 22 Aug 2017 23:35:38 -0400 Date: Wed, 23 Aug 2017 13:35:35 +1000 From: Stephen Rothwell To: jeffy Cc: Nicholas Piggin , Thomas Gleixner , akpm@linux-foundation.org, John Stultz , Stephen Boyd , Jonathan.Cameron@huawei.com, paulmck@linux.vnet.ibm.com, mpe@ellerman.id.au, dzickus@redhat.com, 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 Message-ID: <20170823133535.0b53f6d5@canb.auug.org.au> In-Reply-To: <599CF4C4.2070703@rock-chips.com> References: <20170822084348.21436-1-npiggin@gmail.com> <599CF4C4.2070703@rock-chips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi jeffy, On Wed, 23 Aug 2017 11:21:40 +0800 jeffy wrote: > > 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) I had the same problem with a powerpc le qemu boot. Paul has now removed v1 from his rcu tree, so it will not be in linux-next today. -- Cheers, Stephen Rothwell