Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751927AbaJBLJd (ORCPT ); Thu, 2 Oct 2014 07:09:33 -0400 Received: from casper.infradead.org ([85.118.1.10]:55883 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750987AbaJBLJc (ORCPT ); Thu, 2 Oct 2014 07:09:32 -0400 Date: Thu, 2 Oct 2014 13:09:27 +0200 From: Peter Zijlstra To: Fengguang Wu Cc: Jet Chen , Su Tao , Yuanhan Liu , LKP , linux-kernel@vger.kernel.org, Marcel Holtmann , Peter Hurley Subject: Re: [rfcomm_run] WARNING: CPU: 1 PID: 79 at kernel/sched/core.c:7156 __might_sleep() Message-ID: <20141002110927.GE2849@worktop.programming.kicks-ass.net> References: <20140930080228.GD9561@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140930080228.GD9561@wfg-t540p.sh.intel.com> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 30, 2014 at 04:02:28PM +0800, Fengguang Wu wrote: > Hi Peter, > > We possibly find a rfcomm bug (maintainers CCed) exposed by your debug patch > > [ 1.861895] NET: Registered protocol family 5 > [ 1.862978] Bluetooth: RFCOMM TTY layer initialized > [ 1.863099] ------------[ cut here ]------------ > [ 1.863105] WARNING: CPU: 1 PID: 79 at kernel/sched/core.c:7156 __might_sleep+0x17d/0x1a1() > [ 1.863112] do not call blocking ops when !TASK_RUNNING; state=1 set at [] rfcomm_run+0xdf/0x130e > [ 1.863591] [] ? kthread_stop+0x53/0x53 > [ 1.864906] [] dump_stack+0x48/0x60 > [ 1.866298] [] ? rfcomm_run+0xdf/0x130e Ha yes, rfcomm_run is a complete buggy mess indeed. Lemme go see what I can make of it. -- 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/