From: peter@hurleysoftware.com (Peter Hurley)
To: linux-arm-kernel@lists.infradead.org
Subject: [REGRESSION][3.8.-rc1][ INFO: possible circular locking dependency detected ]
Date: Thu, 27 Dec 2012 08:03:24 -0500 [thread overview]
Message-ID: <1356613404.16896.4.camel@thor.lan> (raw)
In-Reply-To: <20121227083618.GA9775@S2101-09.ap.freescale.net>
On Thu, 2012-12-27 at 16:36 +0800, Shawn Guo wrote:
> On Wed, Dec 26, 2012 at 10:34:39AM +0800, Shawn Guo wrote:
> > It seems that I'm running into the same locking issue. My setup is:
> >
> > - i.MX28 (ARM)
> > - v3.8-rc1
> > - mxs_defconfig
> - The warning is seen when LCD is blanking
> >
>
> The warning disappears after reverting patch daee779 (console: implement
> lockdep support for console_lock). Is it suggesting that the mxs
> frame buffer driver (drivers/video/mxsfb.c) is doing something bad?
>
> Shawn
>
> >
> > [ 602.229899] ======================================================
> > [ 602.229905] [ INFO: possible circular locking dependency detected ]
> > [ 602.229926] 3.8.0-rc1-00003-gde4ae7f #767 Not tainted
> > [ 602.229933] -------------------------------------------------------
> > [ 602.229951] kworker/0:1/21 is trying to acquire lock:
> > [ 602.230037] ((fb_notifier_list).rwsem){.+.+.+}, at: [<c0041f34>] __blocking_notifier_call_chain+0x2c/0x60
You want this patch https://patchwork.kernel.org/patch/1757061/
WARNING: multiple messages have this Message-ID (diff)
From: Peter Hurley <peter@hurleysoftware.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Maciej Rutecki <maciej.rutecki@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION][3.8.-rc1][ INFO: possible circular locking dependency detected ]
Date: Thu, 27 Dec 2012 08:03:24 -0500 [thread overview]
Message-ID: <1356613404.16896.4.camel@thor.lan> (raw)
In-Reply-To: <20121227083618.GA9775@S2101-09.ap.freescale.net>
On Thu, 2012-12-27 at 16:36 +0800, Shawn Guo wrote:
> On Wed, Dec 26, 2012 at 10:34:39AM +0800, Shawn Guo wrote:
> > It seems that I'm running into the same locking issue. My setup is:
> >
> > - i.MX28 (ARM)
> > - v3.8-rc1
> > - mxs_defconfig
> - The warning is seen when LCD is blanking
> >
>
> The warning disappears after reverting patch daee779 (console: implement
> lockdep support for console_lock). Is it suggesting that the mxs
> frame buffer driver (drivers/video/mxsfb.c) is doing something bad?
>
> Shawn
>
> >
> > [ 602.229899] ======================================================
> > [ 602.229905] [ INFO: possible circular locking dependency detected ]
> > [ 602.229926] 3.8.0-rc1-00003-gde4ae7f #767 Not tainted
> > [ 602.229933] -------------------------------------------------------
> > [ 602.229951] kworker/0:1/21 is trying to acquire lock:
> > [ 602.230037] ((fb_notifier_list).rwsem){.+.+.+}, at: [<c0041f34>] __blocking_notifier_call_chain+0x2c/0x60
You want this patch https://patchwork.kernel.org/patch/1757061/
next prev parent reply other threads:[~2012-12-27 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 15:28 [REGRESSION][3.8.-rc1][ INFO: possible circular locking dependency detected ] Maciej Rutecki
2012-12-23 21:34 ` Christian Kujau
2012-12-23 21:34 ` Christian Kujau
2012-12-26 8:18 ` Li Zhong
2012-12-26 8:18 ` Li Zhong
2013-01-04 4:31 ` Christian Kujau
2013-01-04 4:31 ` Christian Kujau
2013-01-27 23:02 ` Christian Kujau
2012-12-26 2:34 ` Shawn Guo
2012-12-26 2:34 ` Shawn Guo
2012-12-27 8:36 ` Shawn Guo
2012-12-27 8:36 ` Shawn Guo
2012-12-27 13:03 ` Peter Hurley [this message]
2012-12-27 13:03 ` Peter Hurley
2012-12-28 11:45 ` Shawn Guo
2012-12-28 11:45 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1356613404.16896.4.camel@thor.lan \
--to=peter@hurleysoftware.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.