On patchwork kms_pipe_crc_basic/suspend-read-crc-pipe-c hangs on CI on SKL 6260-U Test kms_pipe_crc_basic: Subgroup suspend-read-crc-pipe-c: pass -> INCOMPLETE (fi-skl-6260u) Marking this test unstable / known issue due to same run passes on next run. Failure: https://lists.freedesktop.org/archives/intel-gfx/2017-February/119389.html Success: https://patchwork.freedesktop.org/series/19329/ Unfortunately not data available for earlier run. But passes on CI runs in general: https://intel-gfx-ci.01.org/CI/fi-skl-6260u.html
Same now on read-crc-pipe-b. https://intel-gfx-ci.01.org/CI/CI_DRM_2192/fi-skl-6260u/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
Could not reproduce on Celeron(R) CPU G3900 with drm-tip: 2017y-02m-16d-10h-06m-42s and config 2192. crc-pipe-c test was skipped on this machine, crc-pipe-b tried 32 times.
last line in dmesg: [ 421.699056] [IGT] kms_pipe_crc_basic: starting subtest suspend-read-crc-pipe-B I.e. this is one of the busg where we have lost contact with the DUT during suspend-resume and can't get any information on what that has happened. We are working on a solution to use pstore to maybe get more information when this happens. I set lower importance
Move to staging?
Close as invalid, insufficient data. Moving bugs onto a staging pile that no one looks at isn't useful.
But before you do that, double-check we really don't have any other machine that hits this.
(In reply to Daniel Vetter from comment #6) > But before you do that, double-check we really don't have any other machine > that hits this. I really would like to keep bugs like this lying around, in the needinfo state, because it may not be useful for you as developers, but it is for CI engineers who will need to take action on them and make sure that next time it occurs, we have the necessary data to provide developers. How does this sound?
not sure living bugs in the Need info is the correct procedure, I see the point of keeping track but I think should also be a different way. Leaving bugs open just as reference? the same would work leaving them close (not a bug)
*** This bug has been marked as a duplicate of bug 100461 ***
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.