From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jani Nikula Subject: Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Date: Fri, 16 Sep 2016 09:57:07 +0300 Message-ID: <87a8f8pc1o.fsf@intel.com> References: <20160913202350.GA30707@amd> <87h99isuv2.fsf@intel.com> <87h99iraw4.fsf@intel.com> <5982533.muSuxQdgoA@merkaba> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <5982533.muSuxQdgoA@merkaba> Sender: linux-kernel-owner@vger.kernel.org To: Martin Steigerwald Cc: Pavel Machek , kernel list , daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, "Rafael J. Wysocki" List-Id: intel-gfx@lists.freedesktop.org On Thu, 15 Sep 2016, Martin Steigerwald wrote: > Am Mittwoch, 14. September 2016, 14:14:35 CEST schrieb Jani Nikula: >> On Wed, 14 Sep 2016, Jani Nikula wrote: >> > On Wed, 14 Sep 2016, Pavel Machek wrote: >> >> For the "sometimes need xrandr after resume": I don't think I can >> >> bisect that. It only happens sometimes :-(. But there's something >> >> helpful in the logs: >> >> >> >> [ 1856.218863] [drm:drm_edid_block_valid] *ERROR* EDID checksum is >> >> invalid, remainder is 130 >> >> [ 1856.218863] Raw EDID: >> >> [ 1856.218863] 00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] [drm:drm_edid_block_valid] *ERROR* EDID checksum is >> >> invalid, remainder is 130 >> >> [ 1856.218863] Raw EDID: >> >> [ 1856.218863] 00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] [drm:drm_edid_block_valid] *ERROR* EDID checksum is >> >> invalid, remainder is 130 >> >> [ 1856.218863] Raw EDID: >> >> [ 1856.218863] 00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] [drm:drm_edid_block_valid] *ERROR* EDID checksum is >> >> invalid, remainder is 130 >> >> [ 1856.218863] Raw EDID: >> >> [ 1856.218863] 00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >> >> [ 1856.218863] i915 0000:00:02.0: HDMI-A-1: EDID block 0 invalid. >> > >> > Pavel, Martin, do you always see this when the display fails to resume? >> > Is it HDMI/DVI for both of you? >> >> Please try this patch, backported from our next. > > Was busy up to now, and weekend also quite full already. > > Thing is: I didn´t see this blank screen thing with 4.8-rc6 so far. And I did > not have above EDID stuff in my log either. So I first wait whether I see > blank screen again and if so, then know that a test would make sense. Maybe I > see it before I complete a rc7 or rc8 (if there will be one), then I would > include the patch of course. N.b. it's entirely possible you and Pavel have different issues. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center