Created attachment 730937 [details] messages Description of problem: This happens if one leaves the console at the login prompt. After some time, the vt goes black, because of some power saving feature, most likely. But when one presses a key, the console returns, but with this error. After that, the vt is still usable, no crash. Version-Release number of selected component (if applicable): F19a TC3 (19.14) Kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 How reproducible: always Steps to Reproduce: 1. boot, install 2. switch to VT2 in case of using xorg and some window manager 3. wait for the screen to go black 4. press any key to use the VT Actual results: the error is issued, but the system is still usable. Expected results: no issue. Additional info: Apr 2 14:00:48 localhost kernel: [10073.068379] Apr 2 14:00:48 localhost kernel: [10073.068380] ====================================================== Apr 2 14:00:48 localhost kernel: [10073.068381] [ INFO: possible circular locking dependency detected ] Apr 2 14:00:48 localhost kernel: [10073.068383] 3.9.0-0.rc4.git0.1.fc19.x86_64 #1 Not tainted Apr 2 14:00:48 localhost kernel: [10073.068383] ------------------------------------------------------- Apr 2 14:00:48 localhost kernel: [10073.068385] kworker/0:1/1786 is trying to acquire lock: Apr 2 14:00:48 localhost kernel: [10073.068391] (&fb_info->lock){+.+.+.}, at: [<ffffffff813aa03d>] lock_fb_info+0x1d/0x50 Apr 2 14:00:48 localhost kernel: [10073.068391] Apr 2 14:00:48 localhost kernel: [10073.068391] but task is already holding lock: Apr 2 14:00:48 localhost kernel: [10073.068395] (console_lock){+.+.+.}, at: [<ffffffff81444a53>] console_callback+0x13/0x180 Apr 2 14:00:48 localhost kernel: [10073.068396] Apr 2 14:00:48 localhost kernel: [10073.068396] which lock already depends on the new lock. Apr 2 14:00:48 localhost kernel: [10073.068396] Apr 2 14:00:48 localhost kernel: [10073.068396] Apr 2 14:00:48 localhost kernel: [10073.068396] the existing dependency chain (in reverse order) is: Apr 2 14:00:48 localhost kernel: [10073.068398] Apr 2 14:00:48 localhost kernel: [10073.068398] -> #1 (console_lock){+.+.+.}: Apr 2 14:00:48 localhost kernel: [10073.068400] [<ffffffff810daed2>] lock_acquire+0xa2/0x1f0 Apr 2 14:00:48 localhost kernel: [10073.068403] [<ffffffff8106a9f7>] console_lock+0x77/0x80 Apr 2 14:00:48 localhost kernel: [10073.068405] [<ffffffff813ab05d>] register_framebuffer+0x1bd/0x310 Apr 2 14:00:48 localhost kernel: [10073.068407] [<ffffffff81f53ac3>] vesafb_probe+0x6e5/0x760 Apr 2 14:00:48 localhost kernel: [10073.068410] [<ffffffff814727cc>] platform_drv_probe+0x3c/0x70 Apr 2 14:00:48 localhost kernel: [10073.068412] [<ffffffff814704e7>] driver_probe_device+0x87/0x390 Apr 2 14:00:48 localhost kernel: [10073.068413] [<ffffffff814708c3>] __driver_attach+0x93/0xa0 Apr 2 14:00:48 localhost kernel: [10073.068415] [<ffffffff8146e443>] bus_for_each_dev+0x63/0xa0 Apr 2 14:00:48 localhost kernel: [10073.068417] [<ffffffff8146ff3e>] driver_attach+0x1e/0x20 Apr 2 14:00:48 localhost kernel: [10073.068418] [<ffffffff8146fac0>] bus_add_driver+0x1f0/0x2b0 Apr 2 14:00:48 localhost kernel: [10073.068420] [<ffffffff81470f41>] driver_register+0x71/0x150 Apr 2 14:00:48 localhost kernel: [10073.068421] [<ffffffff814725c6>] platform_driver_register+0x46/0x50 Apr 2 14:00:48 localhost kernel: [10073.068423] [<ffffffff8147268b>] platform_driver_probe+0x1b/0xb0 Apr 2 14:00:48 localhost kernel: [10073.068425] [<ffffffff81f533a3>] vesafb_init+0x20d/0x248 Apr 2 14:00:48 localhost kernel: [10073.068427] [<ffffffff8100210a>] do_one_initcall+0x10a/0x160 Apr 2 14:00:48 localhost kernel: [10073.068429] [<ffffffff81f21096>] kernel_init_freeable+0x17c/0x202 Apr 2 14:00:48 localhost kernel: [10073.068431] [<ffffffff816fd0de>] kernel_init+0xe/0x190 Apr 2 14:00:48 localhost kernel: [10073.068433] [<ffffffff8172726c>] ret_from_fork+0x7c/0xb0 Apr 2 14:00:48 localhost kernel: [10073.068435] Apr 2 14:00:48 localhost kernel: [10073.068435] -> #0 (&fb_info->lock){+.+.+.}: Apr 2 14:00:48 localhost kernel: [10073.068437] [<ffffffff810da6f6>] __lock_acquire+0x1a36/0x1a60 Apr 2 14:00:48 localhost kernel: [10073.068438] [<ffffffff810daed2>] lock_acquire+0xa2/0x1f0 Apr 2 14:00:48 localhost kernel: [10073.068441] [<ffffffff8171a0d0>] mutex_lock_nested+0x80/0x3c0 Apr 2 14:00:48 localhost kernel: [10073.068442] [<ffffffff813aa03d>] lock_fb_info+0x1d/0x50 Apr 2 14:00:48 localhost kernel: [10073.068444] [<ffffffff813b70eb>] fbcon_blank+0x28b/0x2d0 Apr 2 14:00:48 localhost kernel: [10073.068445] [<ffffffff81442698>] do_blank_screen+0x1d8/0x280 Apr 2 14:00:48 localhost kernel: [10073.068447] [<ffffffff81444aa8>] console_callback+0x68/0x180 Apr 2 14:00:48 localhost kernel: [10073.068449] [<ffffffff8108e73a>] process_one_work+0x20a/0x690 Apr 2 14:00:48 localhost kernel: [10073.068450] [<ffffffff8108ef41>] worker_thread+0x111/0x3c0 Apr 2 14:00:48 localhost kernel: [10073.068452] [<ffffffff810948fd>] kthread+0xed/0x100 Apr 2 14:00:48 localhost kernel: [10073.068454] [<ffffffff8172726c>] ret_from_fork+0x7c/0xb0 Apr 2 14:00:48 localhost kernel: [10073.068454] Apr 2 14:00:48 localhost kernel: [10073.068454] other info that might help us debug this: Apr 2 14:00:48 localhost kernel: [10073.068454] Apr 2 14:00:48 localhost kernel: [10073.068455] Possible unsafe locking scenario: Apr 2 14:00:48 localhost kernel: [10073.068455] Apr 2 14:00:48 localhost kernel: [10073.068455] CPU0 CPU1 Apr 2 14:00:48 localhost kernel: [10073.068455] ---- ---- Apr 2 14:00:48 localhost kernel: [10073.068456] lock(console_lock); Apr 2 14:00:48 localhost kernel: [10073.068457] lock(&fb_info->lock); Apr 2 14:00:48 localhost kernel: [10073.068458] lock(console_lock); Apr 2 14:00:48 localhost kernel: [10073.068459] lock(&fb_info->lock); Apr 2 14:00:48 localhost kernel: [10073.068460] Apr 2 14:00:48 localhost kernel: [10073.068460] *** DEADLOCK *** Apr 2 14:00:48 localhost kernel: [10073.068460] Apr 2 14:00:48 localhost kernel: [10073.068460] 3 locks held by kworker/0:1/1786: Apr 2 14:00:48 localhost kernel: [10073.068463] #0: (events){.+.+.+}, at: [<ffffffff8108e6ce>] process_one_work+0x19e/0x690 Apr 2 14:00:48 localhost kernel: [10073.068465] #1: (console_work){+.+...}, at: [<ffffffff8108e6ce>] process_one_work+0x19e/0x690 Apr 2 14:00:48 localhost kernel: [10073.068468] #2: (console_lock){+.+.+.}, at: [<ffffffff81444a53>] console_callback+0x13/0x180 Apr 2 14:00:48 localhost kernel: [10073.068468] Apr 2 14:00:48 localhost kernel: [10073.068468] stack backtrace: Apr 2 14:00:48 localhost kernel: [10073.068470] Pid: 1786, comm: kworker/0:1 Not tainted 3.9.0-0.rc4.git0.1.fc19.x86_64 #1 Apr 2 14:00:48 localhost kernel: [10073.068470] Call Trace: Apr 2 14:00:48 localhost kernel: [10073.068474] [<ffffffff8171191f>] print_circular_bug+0x201/0x20f Apr 2 14:00:48 localhost kernel: [10073.068476] [<ffffffff810da6f6>] __lock_acquire+0x1a36/0x1a60 Apr 2 14:00:48 localhost kernel: [10073.068478] [<ffffffff8171e3f3>] ? retint_restore_args+0x13/0x13 Apr 2 14:00:48 localhost kernel: [10073.068480] [<ffffffff810daed2>] lock_acquire+0xa2/0x1f0 Apr 2 14:00:48 localhost kernel: [10073.068482] [<ffffffff813aa03d>] ? lock_fb_info+0x1d/0x50 Apr 2 14:00:48 localhost kernel: [10073.068484] [<ffffffff8171a0d0>] mutex_lock_nested+0x80/0x3c0 Apr 2 14:00:48 localhost kernel: [10073.068485] [<ffffffff813aa03d>] ? lock_fb_info+0x1d/0x50 Apr 2 14:00:48 localhost kernel: [10073.068487] [<ffffffff813aa03d>] ? lock_fb_info+0x1d/0x50 Apr 2 14:00:48 localhost kernel: [10073.068488] [<ffffffff813b91ae>] ? bit_clear+0xce/0x100 Apr 2 14:00:48 localhost kernel: [10073.068490] [<ffffffff813aa03d>] lock_fb_info+0x1d/0x50 Apr 2 14:00:48 localhost kernel: [10073.068491] [<ffffffff813b70eb>] fbcon_blank+0x28b/0x2d0 Apr 2 14:00:48 localhost kernel: [10073.068494] [<ffffffff8171d6c6>] ? _raw_spin_unlock_irqrestore+0x36/0x70 Apr 2 14:00:48 localhost kernel: [10073.068495] [<ffffffff810d88dd>] ? trace_hardirqs_on_caller+0xfd/0x190 Apr 2 14:00:48 localhost kernel: [10073.068497] [<ffffffff810d897d>] ? trace_hardirqs_on+0xd/0x10 Apr 2 14:00:48 localhost kernel: [10073.068499] [<ffffffff8107bcdb>] ? try_to_del_timer_sync+0x5b/0x80 Apr 2 14:00:48 localhost kernel: [10073.068501] [<ffffffff81442698>] do_blank_screen+0x1d8/0x280 Apr 2 14:00:48 localhost kernel: [10073.068503] [<ffffffff81444aa8>] console_callback+0x68/0x180 Apr 2 14:00:48 localhost kernel: [10073.068504] [<ffffffff8108e73a>] process_one_work+0x20a/0x690 Apr 2 14:00:48 localhost kernel: [10073.068506] [<ffffffff8108e6ce>] ? process_one_work+0x19e/0x690 Apr 2 14:00:48 localhost kernel: [10073.068507] [<ffffffff8108ef41>] worker_thread+0x111/0x3c0 Apr 2 14:00:48 localhost kernel: [10073.068509] [<ffffffff8108ee30>] ? rescuer_thread+0x270/0x270 Apr 2 14:00:48 localhost kernel: [10073.068511] [<ffffffff810948fd>] kthread+0xed/0x100 Apr 2 14:00:48 localhost kernel: [10073.068514] [<ffffffff81094810>] ? insert_kthread_work+0x80/0x80 Apr 2 14:00:48 localhost kernel: [10073.068515] [<ffffffff8172726c>] ret_from_fork+0x7c/0xb0 Apr 2 14:00:48 localhost kernel: [10073.068517] [<ffffffff81094810>] ? insert_kthread_work+0x80/0x80
Additional Info: Host: F17 x86_64, using KVM with SPICE/QLX
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.