[Bug 102261] [CI] rtcwake failed with 256

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Oct 20 14:01:06 UTC 2017


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

--- Comment #15 from Marta Löfstedt <marta.lofstedt at intel.com> ---
(In reply to Marta Löfstedt from comment #8)
> After 4.14.0-rc1 KBL-shards either have the rtcwake failed with 256 or
> incompletes.
> 
> Some incomplete runs with pstore:
> 
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3102/shard-kbl4/
> igt at gem_exec_suspend@basic-S4.html
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3104/shard-kbl2/
> igt at gem_exec_suspend@basic-S4.html
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3108/shard-kbl5/
> igt at gem_exec_suspend@basic-S4.html
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3109/shard-kbl5/
> igt at gem_exec_suspend@basic-S4.html
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3112/shard-kbl4/
> igt at gem_exec_suspend@basic-S4.html
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3116/shard-kbl5/
> igt at gem_exec_suspend@basic-S4.html
> 
> The backtraces are not identical, but they all have:
> "e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:"

To clarify here is a run where don't get incomplete but hit the failure
described in the first entry for this bug:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3107/shard-kbl2/igt@drv_suspend@debugfs-reader-hibernate.html

However, I have now discussed with Imre and according to him this bug requires
the association with the backtrace that is included in the kernel bugzilla bug
and/or? the string "[  680.783120] fstrim          D    0  1612   1611
0x00000004"

Also, the links from the original entry in this bug is dead.

-- 
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/20171020/7d15f870/attachment-0001.html>


More information about the intel-gfx-bugs mailing list