Bug 99750

Summary: [SKL][BAT] kms_pipe_crc_basic/suspend-read-crc-pipe-c hangs on SKL-6260U
Product: DRI Reporter: Jani Saarinen <jani.saarinen>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: minor    
Priority: low CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: SKL i915 features: display/Other

Description Jani Saarinen 2017-02-10 08:27:36 UTC
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
Comment 2 Dorota Czaplejewicz 2017-02-16 11:04:50 UTC
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.
Comment 3 Marta Löfstedt 2017-03-03 07:51:10 UTC
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
Comment 4 Marta Löfstedt 2017-03-03 08:24:48 UTC
Move to staging?
Comment 5 Daniel Vetter 2017-03-06 09:08:04 UTC
Close as invalid, insufficient data. Moving bugs onto a staging pile that no one looks at isn't useful.
Comment 6 Daniel Vetter 2017-03-06 09:08:37 UTC
But before you do that, double-check we really don't have any other machine that hits this.
Comment 7 Martin Peres 2017-03-06 10:31:43 UTC
(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?
Comment 8 Ricardo 2017-03-07 22:22:26 UTC
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)
Comment 9 Jani Saarinen 2017-03-30 06:32:15 UTC

*** 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.