From: Jani Nikula <jani.nikula@linux.intel.com>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
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 [thread overview]
Message-ID: <87a8f8pc1o.fsf@intel.com> (raw)
In-Reply-To: <5982533.muSuxQdgoA@merkaba>
On Thu, 15 Sep 2016, Martin Steigerwald <martin@lichtvoll.de> wrote:
> Am Mittwoch, 14. September 2016, 14:14:35 CEST schrieb Jani Nikula:
>> On Wed, 14 Sep 2016, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> > On Wed, 14 Sep 2016, Pavel Machek <pavel@ucw.cz> 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
next prev parent reply other threads:[~2016-09-16 6:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 20:23 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Pavel Machek
2016-09-13 20:38 ` Martin Steigerwald
2016-09-14 7:43 ` Pavel Machek
2016-09-14 10:03 ` Jani Nikula
2016-09-13 21:04 ` Pavel Machek
2016-09-14 7:38 ` Jani Nikula
2016-09-14 7:45 ` Jani Nikula
2016-09-14 7:54 ` Pavel Machek
2016-09-14 9:17 ` Jani Nikula
2016-09-14 11:14 ` Jani Nikula
2016-09-15 15:34 ` Martin Steigerwald
2016-09-16 6:57 ` Jani Nikula [this message]
2016-10-18 14:13 ` Pavel Machek
2016-09-14 11:32 ` Martin Steigerwald
2016-09-14 10:33 ` [Intel-gfx] " Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8f8pc1o.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).