On Fri, Oct 14, 2016 at 01:46:37PM +0300, Ville Syrjälä wrote: > On Thu, Oct 13, 2016 at 08:43:55PM +0100, Chris Wilson wrote: > > Currently, if drm.debug is enabled, we get a DRM_ERROR message on the > > intermediate edid reads. This causes transient failures in CI which > > flags up the sporadic EDID read failures, which are recovered by > > rereading the EDID automatically. This patch combines the reporting done > > by drm_do_get_edid() itself with the bad block printing from > > get_edid_block(), into a single warning associated with the connector > > once all attempts to retrieve the EDID fail. > > One question is why have been getting more of these corrupt EDID reads > recently. Due to your gmbus change, or the live status revert perhaps? The recent reports are from a new Ironlake setup aiui. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
