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

Groups > linux.kernel > #1503020

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

From Pavel Machek <pavel@ucw.cz>
Newsgroups linux.kernel
Subject Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Date 2016-10-18 16:20 +0200
Message-ID <stDpf-2Og-7@gated-at.bofh.it> (permalink)
References (1 earlier) <sh37P-7gw-1@gated-at.bofh.it> <shcXv-6ki-3@gated-at.bofh.it> <shdgS-6sF-15@gated-at.bofh.it> <shewh-7tn-7@gated-at.bofh.it> <shgoq-ao-35@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi!

On Wed 2016-09-14 14:14:35, Jani Nikula wrote:
> 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.

Sorry, spam filter hidden your emails.

I believe I still see the issue on v4.9-rc1. ... does it still make
sense to retry the patch?

What I also is re-aranged windows. So I get resume, I get both
monitors, but I also see that X windows lost connection with the big
monitor (and re-arranged my windows for me).

Oh and I guess I should mention:

1) Yes, I only see the issue on the DVI output. VGA seems to work.

2) I do have power switch on the monitors, so it is possible that
during resume, monitors have no AC power. (Not merely turned off by
the soft switch. No AC power.)

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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

Thread

Re: 4.8-rc1: it is now common that machine needs re-run of xrandr  after resume Pavel Machek <pavel@ucw.cz> - 2016-10-18 16:20 +0200

csiph-web