Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1483213

Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume

From Martin Steigerwald <martin@lichtvoll.de>
Newsgroups linux.kernel
Subject Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Date 2016-09-14 13:40 +0200
Message-ID <shgHL-gO-11@gated-at.bofh.it> (permalink)
References <sh2v8-6Mr-9@gated-at.bofh.it> <shdgS-6sF-15@gated-at.bofh.it> <shewh-7tn-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

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

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

4.8-rc1: it is now common that machine needs re-run of xrandr after  resume Pavel Machek <pavel@ucw.cz> - 2016-09-13 22:30 +0200
  Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Martin Steigerwald <martin@lichtvoll.de> - 2016-09-13 22:50 +0200
    Re: 4.8-rc1: it is now common that machine needs re-run of xrandr  after resume Pavel Machek <pavel@ucw.cz> - 2016-09-14 09:50 +0200
      Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 12:10 +0200
  Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 09:40 +0200
    Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 09:50 +0200
    Re: 4.8-rc1: it is now common that machine needs re-run of xrandr  after resume Pavel Machek <pavel@ucw.cz> - 2016-09-14 10:00 +0200
      Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 11:20 +0200
        Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-14 13:20 +0200
          Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Martin Steigerwald <martin@lichtvoll.de> - 2016-09-15 17:40 +0200
            Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Jani Nikula <jani.nikula@linux.intel.com> - 2016-09-16 09:00 +0200
        Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume Martin Steigerwald <martin@lichtvoll.de> - 2016-09-14 13:40 +0200
  Re: [Intel-gfx] 4.8-rc1: it is now common that machine needs re-run  of xrandr after resume Chris Wilson <chris@chris-wilson.co.uk> - 2016-09-14 12:40 +0200

csiph-web