Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751679AbaJECQB (ORCPT ); Sat, 4 Oct 2014 22:16:01 -0400 Received: from mail-qg0-f50.google.com ([209.85.192.50]:43459 "EHLO mail-qg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751448AbaJECP7 (ORCPT ); Sat, 4 Oct 2014 22:15:59 -0400 Date: Sat, 4 Oct 2014 22:15:56 -0400 From: Tejun Heo To: "Paul E. McKenney" Cc: Dave Jones , Linux Kernel Subject: Re: RCU stalls -> lockup. Message-ID: <20141005021556.GC8549@htj.dyndns.org> References: <20141002175515.GA28665@redhat.com> <20141002193655.GS5015@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141002193655.GS5015@linux.vnet.ibm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 02, 2014 at 12:36:55PM -0700, Paul E. McKenney wrote: > On Thu, Oct 02, 2014 at 01:55:15PM -0400, Dave Jones wrote: > > I just hit this on my box running 3.17rc7 > > It was followed by a userspace lockup. (Could still ping, and sysrq > > from the console, but even getty wasn't responding on the console). > > > > I was trying to reproduce another bug faster, and had ramped up the > > number of processes trinity to uses to 512. This didn't take long > > to fall out.. > > This might be related to an exchange I had with Tejun (CCed), where > the work queues were running all out, preventing any quiescent states > from happening. One fix under consideration is to add a quiescent state, > similar to the one in softirq handling. Dave, can you please test whether the following patch makes a difference if the problem is reproducible? http://lkml.kernel.org/r/20141003153701.7c7da030@jlaw-desktop.mno.stratus.com Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/