Summary: | [APL] [BAT] kms_busy@basic-flip-default-b hangs on CI | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Jani Saarinen <jani.saarinen> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | minor | ||||||
Priority: | highest | CC: | intel-gfx-bugs, tomeu | ||||
Version: | DRI git | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | BXT | i915 features: | |||||
Attachments: |
|
Description
Jani Saarinen
2017-02-09 12:41:57 UTC
Sorry 01.org link: https://intel-gfx-ci.01.org/CI/CI_DRM_2164/fi-bxt-j4205/igt@kms_busy@basic-flip-default-b.html This needs to be a Highest+Blocker. There's no relevant debug information; what is there says that it didn't even start igt@kms_busy@basic-flip-default-b This hanged only once, should we move this to staging to follow? What can we do to provide necessary info when this happens again? If not possible please add code in i915 to provide good information to debug further. 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 bugs 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 Seen also on other APL system with test-c Adding demsg Created attachment 130124 [details]
Dmesg on APL
(In reply to Jani Saarinen from comment #7) > Seen also on other APL system with test-c > Adding demsg Hi Jani, what do you mean by test-c? Copy paste issue. Was trying to say kms_busy@basic-flip-default-c test. Not seen fo the long time. Resolving works for me. Whitelisted again on CI too |
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.