All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
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: Wed, 14 Sep 2016 13:32:59 +0200	[thread overview]
Message-ID: <2198595.9Zm8oKiJA2@merkaba> (raw)
In-Reply-To: <87h99isuv2.fsf@intel.com>

Am Mittwoch, 14. September 2016, 12:17:53 CEST schrieb Jani Nikula:
> 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?

According to zgrep "EDID" /var/log/kern* I don´t have any EDID related error 
messages. I am using DisplayPort cable via ThinkPad Minidock Plus (dock for 
ThinkPad T520) or what it was named.

-- 
Martin

WARNING: multiple messages have this Message-ID (diff)
From: Martin Steigerwald <martin@lichtvoll.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	kernel list <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org, Pavel Machek <pavel@ucw.cz>,
	daniel.vetter@intel.com
Subject: Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Date: Wed, 14 Sep 2016 13:32:59 +0200	[thread overview]
Message-ID: <2198595.9Zm8oKiJA2@merkaba> (raw)
In-Reply-To: <87h99isuv2.fsf@intel.com>

Am Mittwoch, 14. September 2016, 12:17:53 CEST schrieb Jani Nikula:
> 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?

According to zgrep "EDID" /var/log/kern* I don´t have any EDID related error 
messages. I am using DisplayPort cable via ThinkPad Minidock Plus (dock for 
ThinkPad T520) or what it was named.

-- 
Martin
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-09-14 11:33 UTC|newest]

Thread overview: 24+ 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-13 20:38   ` Martin Steigerwald
2016-09-14  7:43   ` Pavel Machek
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:38     ` Jani Nikula
2016-09-14  7:45     ` Jani Nikula
2016-09-14  7:45       ` Jani Nikula
2016-09-14  7:54     ` Pavel Machek
2016-09-14  7:54       ` Pavel Machek
2016-09-14  9:17       ` Jani Nikula
2016-09-14 11:14         ` Jani Nikula
2016-09-14 11:14           ` Jani Nikula
2016-09-15 15:34           ` Martin Steigerwald
2016-09-15 15:34             ` Martin Steigerwald
2016-09-16  6:57             ` Jani Nikula
2016-10-18 14:13           ` Pavel Machek
2016-10-18 14:13             ` Pavel Machek
2016-09-14 11:32         ` Martin Steigerwald [this message]
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=2198595.9Zm8oKiJA2@merkaba \
    --to=martin@lichtvoll.de \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.