Quoting Imre Deak (2019-05-03 11:07:55) > On Fri, May 03, 2019 at 07:50:26AM +0000, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915: Add support for asynchronous display power disabling > > URL : https://patchwork.freedesktop.org/series/60242/ > > State : failure > > > > == Summary == > > > > CI Bug Log - changes from CI_DRM_6032_full -> Patchwork_12955_full > > ==================================================== > > > > Summary > > ------- > > > > **FAILURE** > > > > Serious unknown changes coming with Patchwork_12955_full absolutely need to be > > verified manually. > > > > If you think the reported changes have nothing to do with the changes > > introduced in Patchwork_12955_full, please notify your bug team to allow them > > to document this new failure mode, which will reduce false positives in CI. > > > > > > > > Possible new issues > > ------------------- > > > > Here are the unknown changes that may have been introduced in Patchwork_12955_full: > > > > ### IGT changes ### > > > > #### Possible regressions #### > > > > * igt@gem_persistent_relocs@forked-interruptible-thrashing: > > - shard-glk: [PASS][1] -> [TIMEOUT][2] > > [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6032/shard-glk6/igt@gem_persistent_relocs@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12955/shard-glk7/igt@gem_persistent_relocs@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > Looks like an unrelated issue: on this GLK there are two HDMI displays > connected, so the change shouldn't make any diffence on it. The change > only affects the DP detect and hotplug paths, where we'll do now an > async power domain put. There's no history of glk locking up there, > The machine is still up when the problem happens, the test seems to get > stuck and aborted by the test runner (after ~6mins according to [1]). > > [43/82] (762s left) gem_persistent_relocs (forked-interruptible-thrashing) > Starting subtest: forked-interruptible-thrashing > Timeout. Killing the current test with SIGQUIT. > Timeout. Killing the current test with SIGKILL. and yet it locked up sufficiently to not respond to a signal, suggesting an oops (the test takes 3s normally on glk). -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
