Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757273Ab1CBSM2 (ORCPT ); Wed, 2 Mar 2011 13:12:28 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:36250 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755400Ab1CBSM0 (ORCPT ); Wed, 2 Mar 2011 13:12:26 -0500 X-Authority-Analysis: v=1.1 cv=3uSaImBeuprzHBlOOPjkqgu+7PcxSRW0m2Aphm9Zmck= c=1 sm=0 a=nZ6mVOVMA-0A:10 a=kj9zAlcOel0A:10 a=OPBmh+XkhLl+Enan7BmTLg==:17 a=VwQbUJbxAAAA:8 a=W0vUJOdyAAAA:8 a=CjDJIO3gzgOIPYHx6TkA:9 a=lvnZLYfDRnO9JwEY-54A:7 a=YVg9Ox3Ww-XZ34ujO3iNUdPUQ2sA:4 a=CjuIK1q_8ugA:10 a=x8gzFH9gYPwA:10 a=OPBmh+XkhLl+Enan7BmTLg==:117 X-Cloudmark-Score: 0 X-Originating-IP: 67.242.120.143 Date: Wed, 2 Mar 2011 13:12:23 -0500 From: Steven Rostedt To: Clemens Ladisch Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: (WARNING) possible deadlock in del_timer_sync, called from fbcon_del_cursor_timer Message-ID: <20110302181223.GD9288@home.goodmis.org> References: <4D6BB403.9000908@ladisch.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D6BB403.9000908@ladisch.de> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3287 Lines: 78 On Mon, Feb 28, 2011 at 03:41:07PM +0100, Clemens Ladisch wrote: > While using the FB console, I tried to change the console log level > with SysRq, and got this warning that del_timer_sync() is used in > an interrupt handler: Ug, del_timer_sync() can be called from interrupt context: printk -> vt_console_print -> hide_cursor -> fbcon_cursor -> fbcon_del_cursor_time -> del_timer_sync() printk is allowed to be called from interrupt context. This is indeed a true bug. -- Steve > > SysRq : > ------------[ cut here ]------------ > WARNING: at kernel/timer.c:983 del_timer_sync+0x93/0xae() > Hardware name: System Product Name > Modules linked in: soundcore firewire_ohci firewire_core ohci_hcd ehci_hcd > Pid: 0, comm: kworker/0:1 Not tainted 2.6.38-rc6+ #235 > Call Trace: > [] ? warn_slowpath_common+0x80/0x98 > [] ? warn_slowpath_null+0x15/0x17 > [] ? del_timer_sync+0x93/0xae > [] ? del_timer_sync+0x0/0xae > [] ? fbcon_del_cursor_timer+0x32/0x3d > [] ? fbcon_cursor+0x9a/0x152 > [] ? hide_cursor+0x2c/0x7d > [] ? vt_console_print+0xd9/0x2f7 > [] ? __call_console_drivers+0x67/0x79 > [] ? _call_console_drivers+0x59/0x5d > [] ? console_unlock+0x160/0x1ce > [] ? vprintk+0x358/0x38e > [] ? printk+0x3c/0x3e > [] ? __handle_sysrq+0x23/0x157 > [] ? __handle_sysrq+0x45/0x157 > [] ? sysrq_filter+0x116/0x17b > [] ? input_pass_event+0xbe/0x111 > [] ? input_pass_event+0x0/0x111 > [] ? input_handle_event+0x42a/0x439 > [] ? input_event+0x5b/0x7a > [] ? atkbd_interrupt+0x50f/0x5e0 > [] ? serio_interrupt+0x40/0x7c > [] ? i8042_interrupt+0x289/0x2a3 > [] ? handle_IRQ_event+0x20/0xa8 > [] ? handle_edge_irq+0x103/0x14f > [] ? handle_irq+0x83/0x8c > [] ? do_IRQ+0x48/0xaf > [] ? ret_from_intr+0x0/0x13 > [] ? tick_broadcast_oneshot_control+0x1a/0xfb > [] ? default_idle+0x27/0x43 > [] ? default_idle+0x29/0x43 > [] ? default_idle+0x27/0x43 > [] ? c1e_idle+0xcd/0xf4 > [] ? cpu_idle+0x5f/0x96 > [] ? start_secondary+0x1e3/0x1e5 > ---[ end trace 80565a42945fc993 ]--- > Changing Loglevel > Loglevel set to 3 > > > To add insult to injury, my cursor is configured not to blink. > > > Regards, > Clemens > -- > 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/ -- 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/