[Bug 103313] [CI] igt at kms_cursor_crc@cursor-64x64-suspend - *ERROR* LSPCON mode hasn't settled

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Marta Löfstedt <marta.lofstedt at intel.com> ---
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3275/shard-kbl7/igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-A.html



[  117.120756] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  117.237093] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error
reading LSPCON mode
[  117.237197] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  117.683960] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:
                 TDH                  <0>
                 TDT                  <2>
                 next_to_use          <2>
                 next_to_clean        <0>
               buffer_info[next_to_clean]:
                 time_stamp           <fffd09e5>
                 next_to_watch        <0>
                 jiffies              <fffd3800>
                 next_to_watch.status <0>
               MAC Status             <40000083>
               PHY Status             <796d>
               PHY 1000BASE-T Status  <3800>
               PHY Extended Status    <3000>
               PCI Status             <10>
[  117.828303] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[  117.945327] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error
reading LSPCON mode
[  117.945588] [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
[  118.161717] Setting dangerous option reset - tainting kernel
[  118.162681] Setting dangerous option force_reset_modeset_test - tainting
kernel
[  119.667332] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact 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/20171023/64fc35f4/attachment.html>