https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_19/fi-kbl-r/igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-cpu.html run.log: running: igt/kms_frontbuffer_tracking/fbcpsr-rgb101010-draw-mmap-cpu [70/76] skip: 18, pass: 52 - owatch: TIMEOUT! owatch: timeout for /dev/watchdog0 set to 10 (requested 10) FATAL: command execution failed last dmesg: <7>[ 767.397224] [drm:intel_hpd_irq_handler [i915]] digital hpd port A - short <7>[ 767.397390] [drm:intel_dp_hpd_pulse [i915]] got hpd irq on port A - short <7>[ 767.397714] [drm:intel_dp_aux_xfer [i915]] Forbidden recv_bytes = 0 on aux transaction <7>[ 767.399013] [drm:intel_dp_read_dpcd [i915]] DPCD: 12 14 84 41 00 00 01 01 02 00 00 00 00 0b 00
(In reply to Marta Löfstedt from comment #0) > <7>[ 767.397714] [drm:intel_dp_aux_xfer [i915]] Forbidden recv_bytes = 0 on > aux transaction > <7>[ 767.399013] [drm:intel_dp_read_dpcd [i915]] DPCD: 12 14 84 41 00 00 01 > 01 02 00 00 00 00 0b 00 I don't think I've ever seen this happen. From code: /* * By BSpec: "Message sizes of 0 or >20 are not allowed." * We have no idea of what happened so we return -EBUSY so * drm layer takes care for the necessary retries. */ However, the retry seems to succeed just fine, so I'm not sure if the dmesg part here is a red herring, and the bug is somewhere else.
(In reply to Jani Nikula from comment #1) > (In reply to Marta Löfstedt from comment #0) > > <7>[ 767.397714] [drm:intel_dp_aux_xfer [i915]] Forbidden recv_bytes = 0 on > > aux transaction > > <7>[ 767.399013] [drm:intel_dp_read_dpcd [i915]] DPCD: 12 14 84 41 00 00 01 > > 01 02 00 00 00 00 0b 00 > > I don't think I've ever seen this happen. From code: > > /* > * By BSpec: "Message sizes of 0 or >20 are not allowed." > * We have no idea of what happened so we return -EBUSY so > * drm layer takes care for the necessary retries. > */ > > However, the retry seems to succeed just fine, so I'm not sure if the dmesg > part here is a red herring, and the bug is somewhere else. It could be a duplicate of bug 105959. However, I believe that there is too much time in-between the the backtrace and when owatch triggers.
*** This bug has been marked as a duplicate of bug 105959 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.