From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752590AbdJ3IwT (ORCPT ); Mon, 30 Oct 2017 04:52:19 -0400 Received: from mga06.intel.com ([134.134.136.31]:50379 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752600AbdJ3IwR (ORCPT ); Mon, 30 Oct 2017 04:52:17 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,319,1505804400"; d="scan'208";a="1031088118" Date: Mon, 30 Oct 2017 09:52:10 +0100 From: Fengguang Wu To: Peter Zijlstra , Linus Torvalds Cc: Linux Kernel Mailing List , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , lkp@intel.com Subject: Re: [perf_event_ctx_lock_nested] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97 Message-ID: <20171030085210.eyoaxwg72w4ovqqf@wfg-t540p.sh.intel.com> References: <20171029225155.qcum5i75awrt5tzm@wfg-t540p.sh.intel.com> <20171029230201.neja7ggefrlb7foj@wfg-t540p.sh.intel.com> <20171030084225.n3e2lsrkmjdxh6gf@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20171030084225.n3e2lsrkmjdxh6gf@hirez.programming.kicks-ass.net> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 30, 2017 at 09:42:25AM +0100, Peter Zijlstra wrote: >On Mon, Oct 30, 2017 at 12:02:01AM +0100, Fengguang Wu wrote: >> The dmesg fragment is >> >> [ 40.886662] done >> [ 40.886686] [ 40.905102] capability: warning: `turbostat' uses 32-bit >> capabilities (legacy support in use) >> [ 40.940087] IPMI Device Information >> [ 41.073351] [ 41.076223] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97 >> [ 41.076224] in_atomic(): 1, irqs_disabled(): 0, pid: 14, name: watchdog/0 >> [ 41.076226] CPU: 0 PID: 14 Comm: watchdog/0 Tainted: G O 4.8.0-01558-g21f54dd #1 > ^^^^^^^^^^^^^^^^^^^^ > >That's not 4.14 or even close. Yeah sorry -- it looks like a 0day bug. So the robot stores dmesg files to the wrong commit dir, which made me believe they are all RC6 bugs. Sorry for the noises! Regards, Fengguang