Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756032AbbLBGxG (ORCPT ); Wed, 2 Dec 2015 01:53:06 -0500 Received: from mail-lf0-f68.google.com ([209.85.215.68]:33168 "EHLO mail-lf0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751667AbbLBGxE (ORCPT ); Wed, 2 Dec 2015 01:53:04 -0500 MIME-Version: 1.0 Date: Wed, 2 Dec 2015 17:53:02 +1100 Message-ID: Subject: Re: [BISECTED] rcu_sched self-detected stall since 3.17 From: Ross Green To: linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 481 Lines: 13 I too have traced a similar RCU stall all the way back to 3.17. Seems to affect RCU preempt code as well. I had not been able to find a sure fail way to trigger this and it could take several days running before problem arises. Ross -- 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/