[Bug 92371] [hsw dp mst] external displays unusable on HP Pro x2 612 G1: drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Sun Nov 1 22:36:38 PST 2015
https://bugzilla.kernel.org/show_bug.cgi?id=92371
Henning Rohde <Rohde.Henning at gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #191331|0 |1
is obsolete| |
--- Comment #10 from Henning Rohde <Rohde.Henning at gmx.net> ---
Created attachment 191821
--> https://bugzilla.kernel.org/attachment.cgi?id=191821&action=edit
log from booting 4.3.0-0.rc7.git2.1.fc24 with drm.debug=14
Hi!
Booted with "drm.debug=14", again been able to do login graphically until X11
got up.
Computer hangs completely, no login via ssh possible.
If booted later with display attached via uvcvideo i run into the following
deadlock:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
======================================================
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [ INFO: possible circular locking
dependency detected ]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: 4.3.0-0.rc7.git2.1.fc24.x86_64 #1
Not tainted
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
-------------------------------------------------------
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: Xorg/1465 is trying to acquire
lock:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: (&dmabuf->lock){+.+.+.}, at:
[<ffffffff815a53bf>] dma_buf_vunmap+0x3f/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
but task is already holding lock:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: (&dev->struct_mutex){+.+.+.}, at:
[<ffffffffa007ba9e>] drm_gem_object_handle_unreference_unlocked+0x13e/0x170
[drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
which lock already depends on the
new lock.
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
the existing dependency chain (in
reverse order) is:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
-> #1 (&dev->struct_mutex){+.+.+.}:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff811078ae>]
lock_acquire+0xce/0x1c0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81860a26>]
mutex_lock_interruptible_nested+0x86/0x470
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa0184a19>]
i915_mutex_lock_interruptible+0x29/0x50 [i915]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa0178c18>]
i915_gem_dmabuf_vmap+0x38/0x200 [i915]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff815a52e5>]
dma_buf_vmap+0x55/0xf0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa07cdd73>]
udl_gem_vmap+0x23/0xa0 [udl]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa07cd1b2>]
udl_handle_damage+0x322/0x380 [udl]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa07cb873>]
udl_crtc_mode_set+0x783/0x7f0 [udl]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa012f86c>]
drm_crtc_helper_set_mode+0x29c/0x4d0 [drm_kms_helper]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa0130985>]
drm_crtc_helper_set_config+0xa45/0xbd0 [drm_kms_helper]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa00876d5>]
drm_mode_set_config_internal+0x65/0x110 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa008bd62>]
drm_mode_setcrtc+0x3e2/0x500 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007c8a8>]
drm_ioctl+0x138/0x520 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff812825ae>]
do_vfs_ioctl+0x2ee/0x550
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81282889>]
SyS_ioctl+0x79/0x90
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81864c72>]
entry_SYSCALL_64_fastpath+0x12/0x76
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
-> #0 (&dmabuf->lock){+.+.+.}:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81106caf>]
__lock_acquire+0x191f/0x1ba0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff811078ae>]
lock_acquire+0xce/0x1c0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81860e96>]
mutex_lock_nested+0x86/0x400
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff815a53bf>]
dma_buf_vunmap+0x3f/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa07cde18>]
udl_gem_vunmap+0x28/0x50 [udl]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa07cde5c>]
udl_gem_free_object+0x1c/0x60 [udl]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007b170>]
drm_gem_object_free+0x30/0x50 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007bab8>]
drm_gem_object_handle_unreference_unlocked+0x158/0x170 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007bc56>]
drm_gem_object_release_handle+0x56/0x70 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff8141d058>]
idr_for_each+0xc8/0x130
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007c310>]
drm_gem_release+0x20/0x30 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007b04e>]
drm_release+0x3de/0x4d0 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff8126f315>]
__fput+0xf5/0x200
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff8126f45e>]
____fput+0xe/0x10
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810cdcd3>]
task_work_run+0x73/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810ad714>]
do_exit+0x354/0xc30
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810ae080>]
do_group_exit+0x50/0xc0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810ae104>]
SyS_exit_group+0x14/0x20
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81864c72>]
entry_SYSCALL_64_fastpath+0x12/0x76
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
other info that might help us debug
this:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: Possible unsafe locking scenario:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: CPU0 CPU1
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: ---- ----
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: lock(&dev->struct_mutex);
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
lock(&dmabuf->lock);
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
lock(&dev->struct_mutex);
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: lock(&dmabuf->lock);
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
*** DEADLOCK ***
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: 2 locks held by Xorg/1465:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: #0: (drm_global_mutex){+.+.+.},
at: [<ffffffffa007acaa>] drm_release+0x3a/0x4d0 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: #1: (&dev->struct_mutex){+.+.+.},
at: [<ffffffffa007ba9e>] drm_gem_object_handle_unreference_unlocked+0x13e/0x170
[drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel:
stack backtrace:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: CPU: 1 PID: 1465 Comm: Xorg Not
tainted 4.3.0-0.rc7.git2.1.fc24.x86_64 #1
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: Hardware name: Hewlett-Packard HP
Pro x2 612 G1 Tablet/221B, BIOS M83 Ver. 01.31 07/21/2015
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: 0000000000000000 00000000b4a9c6af
ffff88009248ba20 ffffffff8141bef9
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: ffffffff82c39250 ffff88009248ba60
ffffffff81103973 ffff88009248bac0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: ffff8802362fbf20 0000000000000002
0000000000000002 ffff8802362fb240
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: Call Trace:
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff8141bef9>]
dump_stack+0x4b/0x72
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81103973>]
print_circular_bug+0x1e3/0x250
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81106caf>]
__lock_acquire+0x191f/0x1ba0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81123a7d>] ?
debug_lockdep_rcu_enabled+0x1d/0x20
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81123a7d>] ?
debug_lockdep_rcu_enabled+0x1d/0x20
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff811078ae>]
lock_acquire+0xce/0x1c0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff815a53bf>] ?
dma_buf_vunmap+0x3f/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81860e96>]
mutex_lock_nested+0x86/0x400
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff815a53bf>] ?
dma_buf_vunmap+0x3f/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81861099>] ?
mutex_lock_nested+0x289/0x400
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff815a53bf>] ?
dma_buf_vunmap+0x3f/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81104fa9>] ?
trace_hardirqs_on_caller+0x129/0x1b0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff815a53bf>]
dma_buf_vunmap+0x3f/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa07cde18>]
udl_gem_vunmap+0x28/0x50 [udl]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa07cde5c>]
udl_gem_free_object+0x1c/0x60 [udl]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007b170>]
drm_gem_object_free+0x30/0x50 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007bab8>]
drm_gem_object_handle_unreference_unlocked+0x158/0x170 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa0096625>] ?
drm_vma_node_revoke+0x55/0x80 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007bc56>]
drm_gem_object_release_handle+0x56/0x70 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff8141d058>]
idr_for_each+0xc8/0x130
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007bc00>] ?
drm_gem_dumb_destroy+0x20/0x20 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007c310>]
drm_gem_release+0x20/0x30 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffffa007b04e>]
drm_release+0x3de/0x4d0 [drm]
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff8126f315>]
__fput+0xf5/0x200
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff8126f45e>]
____fput+0xe/0x10
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810cdcd3>]
task_work_run+0x73/0xa0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810ad714>]
do_exit+0x354/0xc30
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81104fa9>] ?
trace_hardirqs_on_caller+0x129/0x1b0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810ae080>]
do_group_exit+0x50/0xc0
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff810ae104>]
SyS_exit_group+0x14/0x20
Nov 02 07:17:38 Fedora22.AmaliX.net kernel: [<ffffffff81864c72>]
entry_SYSCALL_64_fastpath+0x12/0x76
Thanks for your works!
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the intel-gfx-bugs
mailing list