Unfortunately this link is dead on the server: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3877/shard-kbl3/igt@perf_pmu@busy-accuracy-50-vecs0.html However run.log: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3877/shard-kbl3/run7.log running: igt/perf_pmu/busy-accuracy-50-vecs0 [03/98] skip: 3 \ owatch: TIMEOUT! owatch: timeout for /dev/watchdog0 set to 10 (requested 10) FATAL: command execution failed dmesg: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3877/shard-kbl3/dmesg7.log <6>[ 20.498102] Console: switching to colour dummy device 80x25 <7>[ 20.498166] [IGT] perf_pmu: executing <7>[ 20.502090] [IGT] perf_pmu: starting subtest busy-accuracy-50-vecs0 https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3877/shard-kbl3/pstore7-1520326302_Oops_1.log <14>[ 20.502090] [IGT] perf_pmu: starting subtest busy-accuracy-50-vecs0 <12>[ 380.411329] owatch: TIMEOUT! <12>[ 380.411624] owatch: timeout for /dev/watchdog0 set to 10 (requested 10) <6>[ 380.413274] sysrq: SysRq : Trigger a crash <1>[ 380.413706] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_11/fi-cnl-y3/igt@perf_pmu@busy-accuracy-50-bcs0.html run.log: running: igt/perf_pmu/busy-accuracy-50-bcs0 [68/99] skip: 15, pass: 53 | owatch: TIMEOUT! Last dmesg: <7>[ 450.514328] [IGT] perf_pmu: starting subtest busy-accuracy-50-bcs0 <7>[ 453.426037] [drm:edp_panel_vdd_off_sync [i915]] Turning eDP port A VDD off <7>[ 453.426226] [drm:edp_panel_vdd_off_sync [i915]] PP_STATUS: 0x80000008 PP_CONTROL: 0x00000067 pstore: <0>[ 850.475971] gem_exec-2609 3.... 450283856us : reset_all_global_seqno.part.6: bcs0 seqno 3 (current 3) -> 0 ... <0>[ 850.486221] <idle>-0 0..s1 450650256us : execlists_submission_tasklet: bcs0 completed ctx=5 <0>[ 850.486255] kworker/-2304 1.... 450767121us : i915_request_retire: bcs0 fence 78e:19, global_seqno 19, current 19
Lowering to High due to now only seen on drmtip runs.
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.