Bug 93115

Summary: [HSW] *ERROR* mismatch in has_infoframe (expected 1, found 0)
Product: DRI Reporter: Andreas Reis <andreas.reis>
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: major    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg after boot none

Description Andreas Reis 2015-11-26 10:31:59 UTC
Created attachment 120136 [details]
dmesg after boot

On HSW 4770 with current drm-intel-nightly (2015y-11m-25d-17h-08m-45s), dmesg shows repeated entries of

[    1.234004] [drm:intel_pipe_config_compare] *ERROR* mismatch in has_infoframe (expected 1, found 0)
[    1.234004] ------------[ cut here ]------------
[    1.234005] WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:12873 intel_atomic_commit+0x12e4/0x18b0()
[    1.234005] pipe state doesn't match!

Dunno if it's related or even still present, but for the past few days the monitor connected to HDMI1 would sometimes have its green channel maxed out after resuming from DPMS standby, while the other one connected to HDMI2 resumed without issue.
Comment 1 Andreas Reis 2015-11-27 13:19:48 UTC
The green bug doesn't just happen on DPMS, it happens whenever this partiuclar monitor (Crossover 2730MD-P, 2560x1440) is (re-)connected after boot.
Comment 2 Maarten Lankhorst 2015-12-16 09:44:58 UTC

*** This bug has been marked as a duplicate of bug 93119 ***
Comment 3 Maarten Lankhorst 2015-12-16 09:46:14 UTC
Could you file a separate bug for the green channel? Though you probably need to rule out a faulty cable first..
Comment 4 Andreas Reis 2015-12-16 10:39:17 UTC
I could, but it doesn't happen on 4.3 (& Windows) and after [re]booting it's fixed until the connection is interrupted/suspended again on 4.4, coinciding with another has_infoframe warning.

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.