[Bug 90227] New: [BSW regression] *ERROR* mismatch in has_infoframe (expected 1, found 0) when booting with HDMI monitor connected

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 29 01:04:23 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=90227

            Bug ID: 90227
           Summary: [BSW regression]  *ERROR* mismatch in has_infoframe
                    (expected 1, found 0) when booting with HDMI monitor
                    connected
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: jeff.zheng at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 115428
  --> https://bugs.freedesktop.org/attachment.cgi?id=115428&action=edit
dmesg log

==System Environment==
--------------------------
HDMI monitor: ASUS VS239HR
BIOS: V59 
Regression: Yes, don't see this issue on drm-intel-testing-2015-03-13

Non-working platforms: BSW

==kernel==
--------------------------
-testing: drm-intel-testing-2015-04-23 (fails)

==Bug detailed description==
-----------------------------
dmesg shows ERROR when booting with HDMI monitor connected:

[    3.751369] [drm:check_crtc_state [i915]] *ERROR* mismatch in has_infoframe
(expected 1, found 0)


==Reproduce steps==
---------------------------- 
1. Connect VS239HR monitor with HDMI cable and boot
2. dmesg |grep ERROR
[    3.751369] [drm:check_crtc_state [i915]] *ERROR* mismatch in has_infoframe
(expected 1, found 0)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150429/6c042c33/attachment.html>


More information about the intel-gfx-bugs mailing list