Re: Deadlock in fb and tty

2013-09-17 Thread Peter Hurley
On 09/12/2013 09:22 AM, johnflux wrote: The following seems to be better: From d93c1e9761ff66365d658da7d8d0d33823aa946f Mon Sep 17 00:00:00 2001 From: John Tapsell Date: Thu, 12 Sep 2013 09:16:12 +0100 Subject: [PATCH] Fix deadlock between fb_info and console. Do not lock fb_info when callin

Re: Deadlock in fb and tty

2013-09-12 Thread johnflux
_chain(FB_EVENT_CONBLANK, &event); - unlock_fb_info(info); } static int fbcon_blank(struct vc_data *vc, int blank, int mode_switch) -- 1.8.1.2 How can I get this reviewed/acked please? -- View this message in context: http://linux-kernel.2935.n7.nabble.com/Deadlock-in-fb-and-tty-tp717929p7

Re: Deadlock in fb and tty

2013-09-11 Thread Peter Hurley
On 09/11/2013 05:25 AM, John Tapsell wrote: Hi, I'm consistently and constantly hitting a deadlock. console_callback in drivers/tty/vt/vt.c does: console_lock() and then calls: do_blank_screen, which calls: vc->vc_sw->con_blank(..) which can be a pointer to the function: fbc

Deadlock in fb and tty

2013-09-11 Thread John Tapsell
Hi, I'm consistently and constantly hitting a deadlock. console_callback in drivers/tty/vt/vt.c does: console_lock() and then calls: do_blank_screen, which calls: vc->vc_sw->con_blank(..) which can be a pointer to the function: fbcon_blank in video/console/fbcon.c. This is missin