[Bug 110331] [CI][SHARDS] igt@* - incomplete - NMI backtrace for cpu \d skipped: idling at acpi_processor_ffh_cstate_enter

[bugzilla-daemon at freedesktop.org]

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

--- Comment #12 from Anshuman Gupta <anshuman.gupta at intel.com> ---
This issue seems due to kernel task kcompactd0   is blocked for more then 61
seconds.
There is cicular lock dpepedency 

<4>[  938.494641] ======================================================
<4>[  938.494641] WARNING: possible circular locking dependency detected
<4>[  938.494641] 5.1.0-rc3-CI-CI_DRM_5866+ #1 Tainted: G     U           
<4>[  938.494642] ------------------------------------------------------
<4>[  938.494642] kworker/3:11/1689 is trying to acquire lock:
<4>[  938.494642] 000000008b3d0788 ((console_sem).lock){-.-.}, at:
down_trylock+0xa/0x30
<4>[  938.494643] 
<4>[  938.494644] but task is already holding lock:
<4>[  938.494644] 000000002522a786 (&rq->lock){-.-.}, at:
try_to_wake_up+0x1e2/0x5f0
<4>[  938.494645] 
<4>[  938.494645] which lock already depends on the new lock.
<4>[  938.494646] 
<4>[  938.494646] 
<4>[  938.494646] the existing dependency chain (in reverse order) is:

And this test hang-read-crc-pipe checks crc after doing a hang and gpu reset
(not sure what is it).

Can some gem expert provide their comments whether the hang and gpu reset done
by this test is causing to block kcompactd0 for more then 61 seconds.

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