[Bug 112168] [CI][RESUME]igt at kms_* - timeout - Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6]

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=112168

--- Comment #2 from Uma Shankar <uma.shankar at intel.com> ---
I tried to check from display perspective. This looks to be an after affect of
some locking issues caused by tests executed earlier:
Showing all locks held in the system:
 <4>[ 735.147923] 4 locks held by dmesg/1005:
 <4>[ 735.147925] 3 locks held by igt_runner/1022:
 <4>[ 735.147927] #0: ffff88849ead9408 (sb_writers#4)
{.+.+}, at: vfs_write+0x1a4/0x1d0
 <4>[ 735.147933] #1: ffffffff82247a20 (rcu_read_lock){....}, at:
__handle_sysrq+0x0/0x220
 <4>[ 735.147936] #2: ffffffff82247a20 (rcu_read_lock){....}, at:
debug_show_all_locks+0xe/0x1a0
 <4>[ 735.147939] 4 locks held by gem_linear_blit/1049:
 <4>[ 735.147942] #0: ffff88849e2d9408 (sb_writers#14){.+.+} 
, at: vfs_write+0x1a4/0x1d0
 <4>[ 735.147948] #1: ffff888491ada9b0 (&attr->mutex){..}, at:
simple_attr_write+0x36/0xd0
 <4>[ 735.147956] #2: ffff88849b420e70 (&timeline->mutex){..}, at:
intel_gt_retire_requests_timeout+0xe2/0x540 [i915]
 <4>[ 735.147994] #3: ffff888481b5c570 (&gt->reset.mutex){..}, at:
i915_request_wait+0xc9/0x880 [i915]

This is causing the kms_color to wait more than the timeout and causing these
SIGQUIT. 

>From the logs below tests seem to have triggered this:
[IGT] gem_ctx_engines
[IGT] prime_busy
[IGT] i915_pm_rps
[IGT] gem_linear_blits

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191030/6e880fd7/attachment.html>