[Bug 105618] New: [CI] igt at kms_cursor_crc@cursor-128x128-suspend - incomplete - intel ips 0000:00:1f.6: ME failed to update for more than 1s, likely hung

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 20 07:54:48 UTC 2018


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

            Bug ID: 105618
           Summary: [CI] igt at kms_cursor_crc@cursor-128x128-suspend -
                    incomplete - intel ips 0000:00:1f.6: ME failed to
                    update for more than 1s, likely hung
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: marta.lofstedt at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_4/fi-ilk-m540/igt@kms_cursor_crc@cursor-128x128-suspend.html

something went wrong:
run.log:

New build name is 'drmtip_4/fi-ilk-m540/4'
ERROR: remote file operation failed: /opt/jenkins/workspace/CI_IGT_test at
hudson.remoting.Channel at 26abd2ad:fi-ilk-m540:
hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on
fi-ilk-m540 failed. The channel is closing down or has closed down
FATAL: Channel "unknown": Remote call on fi-ilk-m540 failed. The channel is
closing down or has closed down
java.io.EOFException

from dmesg:
<4>[   24.312070] intel ips 0000:00:1f.6: ME failed to update for more than 1s,
likely hung
...
<4>[   96.848140] intel ips 0000:00:1f.6: ME failed to update for more than 1s,
likely hung

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


More information about the intel-gfx-bugs mailing list