| Summary: | [BAT] igt@kms_setmode@basic-clone-single-crtc - dmesg-warn - *ERROR* Atomic update failure on pipe B | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
| 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: | major | ||
| Priority: | high | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | CFL | i915 features: | display/Other |
|
Description
Marta Löfstedt
2017-10-09 13:14:05 UTC
Daniel's patch should minimize these: https://cgit.freedesktop.org/drm-tip/commit/?id=69208c9e1e938cd115fdafdc502b5a7aa99d8d0b Lets keep open to track and see if issues still but lowering priority. We got the warn today on our CFL but with a different test igt@kms_pipe_crc_basic@read-crc-pipe-b. IGT-Version: 1.21-g319a1de (x86_64) (Linux: 4.15.0-rc8-drm-intel-qa-ww3-commit-a5cf4f0+ x86_64) read-crc-pipe-B: Testing connector eDP-1 using pipe B read-crc-pipe-B: Testing connector DP-1 using pipe B Subtest read-crc-pipe-B: SUCCESS (1.863s) [ 438.178706] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=38 end=39) time 205 us, min 1073, max 1079, scanline start 1068, end 1082 https://intel-gfx-ci.01.org/tree/drm-tip/igt@kms_setmode@basic-clone-single-crtc.html is pretty much green on CI now for CFL. Feel free to reopen if there is something I'm missing. (In reply to Rodrigo Vivi from comment #3) > https://intel-gfx-ci.01.org/tree/drm-tip/igt@kms_setmode@basic-clone-single- > crtc.html > > is pretty much green on CI now for CFL. > > Feel free to reopen if there is something I'm missing. Rodrigo, from CI perspective this bug is archived since this particular machine is no longer in our lab. However QA seem to be using it. Closing, please re-open if still occurs. |
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.