Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S936600AbdCYABZ (ORCPT <rfc822;w@1wt.eu>);
        Fri, 24 Mar 2017 20:01:25 -0400
Received: from mail-pf0-f173.google.com ([209.85.192.173]:36655 "EHLO
        mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S933480AbdCYABS (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 24 Mar 2017 20:01:18 -0400
Date: Sat, 25 Mar 2017 09:00:05 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Ott <sebott@linux.vnet.ibm.com>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Petr Mladek <pmladek@suse.com>,
        Heiko Carstens <heiko.carstens@de.ibm.com>,
        linux-kernel@vger.kernel.org
Subject: Re: lockdep warning: console vs. mem hotplug
Message-ID: <20170325000005.GC6356@tigerII.localdomain>
References: <alpine.LFD.2.20.1703201736070.1753@schleppi>
 <20170324123933.78f9c125@gandalf.local.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170324123933.78f9c125@gandalf.local.home>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 350
Lines: 13

Hello,

On (03/24/17 12:39), Steven Rostedt wrote:
[..]
> Is there a stack trace of where the lockdep dump happened? That is
> useful too. Otherwise we don't see where the inverse happened.

Steven, isn't it the inversion I describe in [1] (after the first lockdep
warning)?

[1] lkml.kernel.org/r/20170321044421.GB448@jagdpanzerIV.localdomain

	-ss