[Bug 105128] [CI] igt at kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-cpu - dmesg-warn - *ERROR* dp aux hw did not signal timeout (has irq: 1)!
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Apr 18 11:07:46 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105128
--- Comment #2 from Martin Peres <martin.peres at free.fr> ---
Also seen on hibernate tests:
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_22/fi-kbl-7500u/igt@gem_eio@hibernate.html
[ 59.246542] Setting dangerous option reset - tainting kernel
[ 59.249777] i915 0000:00:02.0: Resetting chip for Manually set wedged engine
mask = ffffffffffffffff
[ 59.254239] Setting dangerous option reset - tainting kernel
[ 64.828941] usb usb1: root hub lost power or was reset
[ 64.828972] usb usb2: root hub lost power or was reset
[ 64.831656] usb usb3: root hub lost power or was reset
[ 64.831659] usb usb4: root hub lost power or was reset
[ 64.891584] [drm:intel_dp_aux_xfer [i915]] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
[ 65.454836] Setting dangerous option reset - tainting kernel
[ 65.455807] i915 0000:00:02.0: Resetting chip for Manually set wedged engine
mask = ffffffffffffffff
[ 71.071867] usb usb1: root hub lost power or was reset
[ 71.071870] usb usb2: root hub lost power or was reset
[ 71.072632] usb usb3: root hub lost power or was reset
[ 71.072634] usb usb4: root hub lost power or was reset
[ 71.691027] Setting dangerous option reset - tainting kernel
[ 71.691650] i915 0000:00:02.0: Resetting chip for Manually set wedged engine
mask = ffffffffffffffff
[ 71.708335] Setting dangerous option reset - tainting kernel
[ 71.708754] i915 0000:00:02.0: Resetting chip for Manually set wedged engine
mask = ffffffffffffffff
--
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/20180418/ab58bdcc/attachment.html>
More information about the intel-gfx-bugs
mailing list