Hide Forgot
Description of problem: When I played webm video in latest google-chrome Additional info: reporter: libreport-2.6.3 [ INFO: possible recursive locking detected ] 4.2.6-300.fc23.x86_64+debug #1 Not tainted --------------------------------------------- systemd-logind/1217 is trying to acquire lock: (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa01bafa9>] i915_gem_unmap_dma_buf+0x39/0x100 [i915] but task is already holding lock: (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa00389de>] drm_gem_object_handle_unreference_unlocked+0x13e/0x170 [drm] other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&dev->struct_mutex); lock(&dev->struct_mutex); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by systemd-logind/1217: #0: (drm_global_mutex){+.+.+.}, at: [<ffffffffa0037bfa>] drm_release+0x3a/0x4d0 [drm] #1: (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa00389de>] drm_gem_object_handle_unreference_unlocked+0x13e/0x170 [drm] stack backtrace: CPU: 2 PID: 1217 Comm: systemd-logind Not tainted 4.2.6-300.fc23.x86_64+debug #1 Hardware name: LENOVO 2349PVG/2349PVG, BIOS G1ETA8WW (2.68 ) 03/06/2015 0000000000000000 00000000fd99cb93 ffff88041de43a28 ffffffff81869b26 0000000000000000 ffffffff82af9b90 ffff88041de43b08 ffffffff8110a188 0000000000000000 0000000000000000 ffff88041de43a58 ffffffff81128500 Call Trace: [<ffffffff81869b26>] dump_stack+0x4c/0x65 [<ffffffff8110a188>] __lock_acquire+0x1cd8/0x1d00 [<ffffffff81128500>] ? wait_rcu_gp+0x70/0xb0 [<ffffffff81026d68>] ? native_sched_clock+0x28/0x90 [<ffffffff8110ab37>] lock_acquire+0xc7/0x270 [<ffffffffa01bafa9>] ? i915_gem_unmap_dma_buf+0x39/0x100 [i915] [<ffffffff8186f73f>] mutex_lock_nested+0x7f/0x3e0 [<ffffffffa01bafa9>] ? i915_gem_unmap_dma_buf+0x39/0x100 [i915] [<ffffffff81026d68>] ? native_sched_clock+0x28/0x90 [<ffffffffa01bafa9>] ? i915_gem_unmap_dma_buf+0x39/0x100 [i915] [<ffffffff810e7e3c>] ? local_clock+0x1c/0x20 [<ffffffffa01bafa9>] i915_gem_unmap_dma_buf+0x39/0x100 [i915] [<ffffffff815add75>] dma_buf_unmap_attachment+0x55/0x80 [<ffffffffa0052862>] drm_prime_gem_destroy+0x22/0x40 [drm] [<ffffffffa0389381>] nouveau_gem_object_del+0x81/0xf0 [nouveau] [<ffffffffa0038247>] drm_gem_object_free+0x27/0x30 [drm] [<ffffffffa00389f8>] drm_gem_object_handle_unreference_unlocked+0x158/0x170 [drm] [<ffffffffa0038b9a>] drm_gem_object_release_handle+0x5a/0x80 [drm] [<ffffffff814217c8>] idr_for_each+0xc8/0x130 [<ffffffffa0038b40>] ? drm_gem_dumb_destroy+0x20/0x20 [drm] [<ffffffffa0039284>] drm_gem_release+0x24/0x40 [drm] [<ffffffffa0037f9e>] drm_release+0x3de/0x4d0 [drm] [<ffffffff81272405>] __fput+0xf5/0x200 [<ffffffff8127255e>] ____fput+0xe/0x10 [<ffffffff810d19cd>] task_work_run+0x8d/0xc0 [<ffffffff8101caad>] do_notify_resume+0x8d/0x90 [<ffffffff818737e6>] int_signal+0x12/0x17
Created attachment 1113609 [details] File: dmesg
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.