From: Krzysztof Helt <krzysztof.h1@wp.pl>
To: Dmitry Baryshkov <dbaryshkov@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, rpurdie@rpsys.net,
adaplas@gmail.com
Subject: Re: [Linux-fbdev-devel] [fbdev] Lockdep error
Date: Tue, 16 Sep 2008 23:39:16 +0200 [thread overview]
Message-ID: <20080916233916.4f9c0dfd.krzysztof.h1@wp.pl> (raw)
In-Reply-To: <20080915122152.GA4570@doriath.ww600.siemens.net>
On Mon, 15 Sep 2008 16:21:52 +0400
Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:
> Hi,
>
> After doing
> # echo 1 > /sys/class/graphics/fb0/blank
> I got the following in my kernel log:
>
> =============================================
> [ INFO: possible recursive locking detected ]
> 2.6.27-rc6-00086-gda63874-dirty #97
> ---------------------------------------------
> echo/1564 is trying to acquire lock:
> ((fb_notifier_list).rwsem){..--}, at: [<c005a384>] __blocking_notifier_call_chain+0x38/0x6c
>
Does the patch below fix the problem for you?
Kind regards,
Krzysztof
diff -urp linux-ref/drivers/video/console/fbcon.c linux-mm/drivers/video/console/fbcon.c
--- linux-ref/drivers/video/console/fbcon.c 2008-09-05 23:38:47.000000000 +0200
+++ linux-mm/drivers/video/console/fbcon.c 2008-09-16 23:30:52.309604454 +0200
@@ -2400,11 +2400,15 @@ static int fbcon_blank(struct vc_data *v
if (!fbcon_is_inactive(vc, info)) {
if (ops->blank_state != blank) {
+ int ret = 1;
+
ops->blank_state = blank;
fbcon_cursor(vc, blank ? CM_ERASE : CM_DRAW);
ops->cursor_flash = (!blank);
- if (fb_blank(info, blank))
+ if (info->fbops->fb_blank)
+ ret = info->fbops->fb_blank(blank, info);
+ if (ret)
fbcon_generic_blank(vc, info, blank);
}
next prev parent reply other threads:[~2008-09-16 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 12:21 Dmitry Baryshkov
2008-09-16 21:39 ` Krzysztof Helt [this message]
2008-09-23 9:53 ` [Linux-fbdev-devel] " Dmitry
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=20080916233916.4f9c0dfd.krzysztof.h1@wp.pl \
--to=krzysztof.h1@wp.pl \
--cc=adaplas@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®