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

Groups > linux.kernel > #1482755 > unrolled thread

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

Started byPavel Machek <pavel@ucw.cz>
First post2016-09-13 22:30 +0200
Last post2016-09-14 12:40 +0200
Articles 13 — 4 participants

Back to article view | Back to linux.kernel

Contents

  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

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

FromPavel Machek <pavel@ucw.cz>
Date2016-09-13 22:30 +0200
Subject4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<sh2v8-6Mr-9@gated-at.bofh.it>
Hi!

I have

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)

In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
in 10 resumes?) get in state where primary monitor (DVI) is dead (in
powersave) and all windows move to secondary monitor (VGA). Running
"xrandr" fixes that.

I'll update to newer rc and see if it happens again, but if you have
any ideas, now would be good time.

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

[toc] | [next] | [standalone]

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

FromMartin Steigerwald <martin@lichtvoll.de>
Date2016-09-13 22:50 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<sh2Ou-6TO-9@gated-at.bofh.it>
In reply to#1482755
Hi.

Am Dienstag, 13. September 2016, 22:23:50 CEST schrieb Pavel Machek: 
> I have
> 
> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> Integrated Graphics Controller (rev 03)

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation 
Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

Phoronix Test Suite system-info:

System Information

Hardware:
Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO 
42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB, 
Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel 2nd 
Generation Core Family IGP, Audio: Conexant CX20590, Monitor: P24T-7 LED, 
Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205

Software:
OS: Debian unstable, Kernel: 4.8.0-rc6-tp520-btrfstrim+ (x86_64), Desktop: KDE 
Frameworks 5, Display Server: X Server 1.18.4, Display Driver: modesetting 
1.18.4, OpenGL: 3.3 Mesa 12.0.2, Compiler: GCC 6.2.0 20160901, File-System: 
btrfs, Screen Resolution: 3840x1080

> In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
> in 10 resumes?) get in state where primary monitor (DVI) is dead (in
> powersave) and all windows move to secondary monitor (VGA). Running
> "xrandr" fixes that.

I have seen this in 4.8 up to rc5 as well. I am not sure yet about rc6 which I 
am currently running.

I didn´t run xrandr by hand. But I ran systemsettings, dragged the second, 
deactivated external display back beneath the internal laptop display, 
activated it again and applied this changes. I think this has a somewhat 
similar effect as Plasma uses RANDR as well.
 
> I'll update to newer rc and see if it happens again, but if you have
> any ideas, now would be good time.

No ideas, sorry.

Thanks,
-- 
Martin

[toc] | [prev] | [next] | [standalone]

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

FromPavel Machek <pavel@ucw.cz>
Date2016-09-14 09:50 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shd7d-6oH-63@gated-at.bofh.it>
In reply to#1482764
On Tue 2016-09-13 22:38:45, Martin Steigerwald wrote:
> Hi.
> 
> Am Dienstag, 13. September 2016, 22:23:50 CEST schrieb Pavel Machek: 
> > I have
> > 
> > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> 
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation 
> Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
> 
> Phoronix Test Suite system-info:

...
> > In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
> > in 10 resumes?) get in state where primary monitor (DVI) is dead (in
> > powersave) and all windows move to secondary monitor (VGA). Running
> > "xrandr" fixes that.
> 
> I have seen this in 4.8 up to rc5 as well. I am not sure yet about rc6 which I 
> am currently running.

Ok, it happened again today, with yesterdays version of 4.8-rc6. I'm
glad I'm not the only one.

Intel folks, any ideas? Can you reproduce it?

Best regards,
								Pavel

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

[toc] | [prev] | [next] | [standalone]

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

FromJani Nikula <jani.nikula@linux.intel.com>
Date2016-09-14 12:10 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shfiG-7ZI-31@gated-at.bofh.it>
In reply to#1483036
On Wed, 14 Sep 2016, Pavel Machek <pavel@ucw.cz> wrote:
> Intel folks, any ideas? Can you reproduce it?

It's possible (but not confirmed yet) we've seen this in our CI, but has
slipped through because it's sporadic.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

[toc] | [prev] | [next] | [standalone]

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

FromJani Nikula <jani.nikula@linux.intel.com>
Date2016-09-14 09:40 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shcXv-6ki-3@gated-at.bofh.it>
In reply to#1482755
On Wed, 14 Sep 2016, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
>> I have
>> 
>> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
>> Integrated Graphics Controller (rev 03)
>> 
>> In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
>> in 10 resumes?) get in state where primary monitor (DVI) is dead (in
>> powersave) and all windows move to secondary monitor (VGA). Running
>> "xrandr" fixes that.
>> 
>> I'll update to newer rc and see if it happens again, but if you have
>> any ideas, now would be good time.
>
> Ok. With -rc6, X are completely broken. I got notification "could not
> restore CRTC config for screen 63" or something like that, and window
> manager just does not start.

Ugh. Can you bisect from v4.7, assuming it worked? That's probably the
fastest way to resolve this.

BR,
Jani.

>
> X log is attached as delme, kernel log as delme2. Nothing too
> suspicious :-(.
>
> 									Pavel

-- 
Jani Nikula, Intel Open Source Technology Center

[toc] | [prev] | [next] | [standalone]

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

FromJani Nikula <jani.nikula@linux.intel.com>
Date2016-09-14 09:50 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shd7c-6oH-53@gated-at.bofh.it>
In reply to#1482993
On Wed, 14 Sep 2016, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 14 Sep 2016, Pavel Machek <pavel@ucw.cz> wrote:
>> Hi!
>>
>>> I have
>>> 
>>> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
>>> Integrated Graphics Controller (rev 03)
>>> 
>>> In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
>>> in 10 resumes?) get in state where primary monitor (DVI) is dead (in
>>> powersave) and all windows move to secondary monitor (VGA). Running
>>> "xrandr" fixes that.
>>> 
>>> I'll update to newer rc and see if it happens again, but if you have
>>> any ideas, now would be good time.
>>
>> Ok. With -rc6, X are completely broken. I got notification "could not
>> restore CRTC config for screen 63" or something like that, and window
>> manager just does not start.
>
> Ugh. Can you bisect from v4.7, assuming it worked? That's probably the
> fastest way to resolve this.

Also, if you don't mind, please file a bug at [1], attaching the logs
there. It'll be easier for me to direct attention and priority to the
bug, which will help you too in the end.

Thanks,
Jani.

[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel

-- 
Jani Nikula, Intel Open Source Technology Center

[toc] | [prev] | [next] | [standalone]

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

FromPavel Machek <pavel@ucw.cz>
Date2016-09-14 10:00 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shdgS-6sF-15@gated-at.bofh.it>
In reply to#1482993
On Wed 2016-09-14 10:38:18, Jani Nikula wrote:
> On Wed, 14 Sep 2016, Pavel Machek <pavel@ucw.cz> wrote:
> > Hi!
> >
> >> I have
> >> 
> >> 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> >> Integrated Graphics Controller (rev 03)
> >> 
> >> In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
> >> in 10 resumes?) get in state where primary monitor (DVI) is dead (in
> >> powersave) and all windows move to secondary monitor (VGA). Running
> >> "xrandr" fixes that.
> >> 
> >> I'll update to newer rc and see if it happens again, but if you have
> >> any ideas, now would be good time.
> >
> > Ok. With -rc6, X are completely broken. I got notification "could not
> > restore CRTC config for screen 63" or something like that, and window
> > manager just does not start.
> 
> Ugh. Can you bisect from v4.7, assuming it worked? That's probably the
> fastest way to resolve this.

The "completely broken" part -- something broke in my userland, as
booting to the old kernel does not fix it. I'll have to figure it out.

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:

Best regards,
								Pavel
								
[ 1856.213154] CPU1 is up
[ 1856.213167] ACPI: Waking up from system sleep state S3
[ 1856.217998] clocksource: Switched to clocksource hpet
[ 1856.218170] uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
[ 1856.218470] uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
[ 1856.218656] uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
[ 1856.218665] uhci_hcd 0000:00:1d.3: System wakeup disabled by ACPI
[ 1856.218863] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
[ 1856.218863] PM: noirq resume of devices complete after 19.597 msecs
[ 1856.218863] PM: early resume of devices complete after 1.092 msecs
[ 1856.218863] usb usb2: root hub lost power or was reset
[ 1856.218863] usb usb3: root hub lost power or was reset
[ 1856.218863] usb usb4: root hub lost power or was reset
[ 1856.218863] usb usb5: root hub lost power or was reset
[ 1856.218863] pcieport 0000:00:1c.1: System wakeup disabled by ACPI
[ 1856.218863] serial 00:03: activated
[ 1856.218863] parport_pc 00:04: activated
[ 1856.218863] rtc_cmos 00:05: System wakeup disabled by ACPI
[ 1856.218863] ata2: port disabled--ignoring
[ 1856.218863] r8169 0000:03:00.0 eth0: link down
[ 1856.218863] sd 2:0:0:0: [sda] Starting disk
[ 1856.218863] sd 2:0:1:0: [sdb] Starting disk
[ 1856.218863] ata4.01: NODEV after polling detection
[ 1856.218863] ata3.01: ACPI cmd ef/03:45:00:00:00:b0 (SET FEATURES)
filtered out
[ 1856.218863] ata3.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES)
filtered out
[ 1856.218863] ata3.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE
LOCK) filtered out
[ 1856.218863] ata3.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES)
filtered out
[ 1856.218863] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[ 1856.218863] ata3.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE
MODE) succeeded
[ 1856.218863] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE
LOCK) filtered out
[ 1856.218863] ata3.00: configured for UDMA/133
[ 1856.218863] ata4.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES)
filtered out
[ 1856.218863] ata4.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES)
filtered out
[ 1856.218863] ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE
LOCK) filtered out
[ 1856.218863] ata3.01: configured for UDMA/133
[ 1856.218863] ata4.00: configured for UDMA/133
[ 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.
[ 1857.416283] r8169 0000:03:00.0 eth0: link up
[ 1858.352216] PM: resume of devices complete after 2990.454 msecs
[ 1858.353245] PM: resume devices took 2.992 seconds
[ 1858.353344] PM: Finishing wakeup.
[ 1858.353346] Restarting tasks ...
[ 1858.353491] usb 1-8: USB disconnect, device number 6
[ 1858.358714] done.
[ 1858.861355] r8169 0000:03:00.0 eth0: link down
[ 1858.861439] r8169 0000:03:00.0 eth0: link down
[ 1860.726118] r8169 0000:03:00.0 eth0: link up
[ 3806.819909] perf: interrupt took too long (3931 > 3922), lowering
kernel.perf_event_max_sample_rate to 50750

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

[toc] | [prev] | [next] | [standalone]

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

FromJani Nikula <jani.nikula@linux.intel.com>
Date2016-09-14 11:20 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shewh-7tn-7@gated-at.bofh.it>
In reply to#1483052
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?


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

[toc] | [prev] | [next] | [standalone]

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

FromJani Nikula <jani.nikula@linux.intel.com>
Date2016-09-14 13:20 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shgoq-ao-35@gated-at.bofh.it>
In reply to#1483119
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.

BR,
Jani.

From c5cec7b2df1a518a632998aecd6f73f3fefe59ec Mon Sep 17 00:00:00 2001
From: David Weinehall <david.weinehall@linux.intel.com>
Date: Wed, 17 Aug 2016 15:47:48 +0300
Subject: [PATCH] Revert "drm/i915: Check live status before reading edid"
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Cc: Jani Nikula <jani.nikula@intel.com>

This reverts commit 237ed86c693d8a8e4db476976aeb30df4deac74b.

Our current implementation of live status check (repeat 9 times
with 10ms delays between each attempt as a workaround for
buggy displays) imposes a rather serious penalty, time wise,
on intel_hdmi_detect().  Since we we already skip live status
checks on platforms before gen 7, and since we seem to have
coped quite well before the live status check was introduced
for newer platforms too, the previous behaviour is probably
preferable, at least unless someone can point to a use-case
that the live status check improves (apart from "Bspec says so".)

Signed-off-by: David Weinehall <david.weinehall@linux.intel.com>
Fixes: 237ed86c693d ("drm/i915: Check live status before reading edid")
Fixes: f8d03ea0053b ("drm/i915: increase the tries for HDMI hotplug live status checking")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97139
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94014
Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: stable@vger.kernel.org # v4.4+
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20160817124748.31208-1-david.weinehall@linux.intel.com

Conflicts:
	drivers/gpu/drm/i915/intel_drv.h
---
 drivers/gpu/drm/i915/intel_dp.c   |  2 +-
 drivers/gpu/drm/i915/intel_drv.h  |  2 --
 drivers/gpu/drm/i915/intel_hdmi.c | 43 +++++++++------------------------------
 3 files changed, 11 insertions(+), 36 deletions(-)

diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 21b04c3eda41..81c9b89b7a38 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -4148,7 +4148,7 @@ static bool bxt_digital_port_connected(struct drm_i915_private *dev_priv,
  *
  * Return %true if @port is connected, %false otherwise.
  */
-bool intel_digital_port_connected(struct drm_i915_private *dev_priv,
+static bool intel_digital_port_connected(struct drm_i915_private *dev_priv,
 					 struct intel_digital_port *port)
 {
 	if (HAS_PCH_IBX(dev_priv))
diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
index ff399b9a5c1f..2c74213a8467 100644
--- a/drivers/gpu/drm/i915/intel_drv.h
+++ b/drivers/gpu/drm/i915/intel_drv.h
@@ -1387,8 +1387,6 @@ void intel_edp_drrs_disable(struct intel_dp *intel_dp);
 void intel_edp_drrs_invalidate(struct drm_device *dev,
 		unsigned frontbuffer_bits);
 void intel_edp_drrs_flush(struct drm_device *dev, unsigned frontbuffer_bits);
-bool intel_digital_port_connected(struct drm_i915_private *dev_priv,
-					 struct intel_digital_port *port);
 
 void
 intel_dp_program_link_training_pattern(struct intel_dp *intel_dp,
diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
index 4df9f384910c..c3aa9e670d15 100644
--- a/drivers/gpu/drm/i915/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/intel_hdmi.c
@@ -1422,24 +1422,22 @@ intel_hdmi_dp_dual_mode_detect(struct drm_connector *connector, bool has_edid)
 }
 
 static bool
-intel_hdmi_set_edid(struct drm_connector *connector, bool force)
+intel_hdmi_set_edid(struct drm_connector *connector)
 {
 	struct drm_i915_private *dev_priv = to_i915(connector->dev);
 	struct intel_hdmi *intel_hdmi = intel_attached_hdmi(connector);
-	struct edid *edid = NULL;
+	struct edid *edid;
 	bool connected = false;
 
-	if (force) {
-		intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);
+	intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);
 
-		edid = drm_get_edid(connector,
-				    intel_gmbus_get_adapter(dev_priv,
-				    intel_hdmi->ddc_bus));
+	edid = drm_get_edid(connector,
+			    intel_gmbus_get_adapter(dev_priv,
+			    intel_hdmi->ddc_bus));
 
-		intel_hdmi_dp_dual_mode_detect(connector, edid != NULL);
+	intel_hdmi_dp_dual_mode_detect(connector, edid != NULL);
 
-		intel_display_power_put(dev_priv, POWER_DOMAIN_GMBUS);
-	}
+	intel_display_power_put(dev_priv, POWER_DOMAIN_GMBUS);
 
 	to_intel_connector(connector)->detect_edid = edid;
 	if (edid && edid->input & DRM_EDID_INPUT_DIGITAL) {
@@ -1465,37 +1463,16 @@ static enum drm_connector_status
 intel_hdmi_detect(struct drm_connector *connector, bool force)
 {
 	enum drm_connector_status status;
-	struct intel_hdmi *intel_hdmi = intel_attached_hdmi(connector);
 	struct drm_i915_private *dev_priv = to_i915(connector->dev);
-	bool live_status = false;
-	unsigned int try;
 
 	DRM_DEBUG_KMS("[CONNECTOR:%d:%s]\n",
 		      connector->base.id, connector->name);
 
 	intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);
 
-	for (try = 0; !live_status && try < 9; try++) {
-		if (try)
-			msleep(10);
-		live_status = intel_digital_port_connected(dev_priv,
-				hdmi_to_dig_port(intel_hdmi));
-	}
-
-	if (!live_status) {
-		DRM_DEBUG_KMS("HDMI live status down\n");
-		/*
-		 * Live status register is not reliable on all intel platforms.
-		 * So consider live_status only for certain platforms, for
-		 * others, read EDID to determine presence of sink.
-		 */
-		if (INTEL_INFO(dev_priv)->gen < 7 || IS_IVYBRIDGE(dev_priv))
-			live_status = true;
-	}
-
 	intel_hdmi_unset_edid(connector);
 
-	if (intel_hdmi_set_edid(connector, live_status)) {
+	if (intel_hdmi_set_edid(connector)) {
 		struct intel_hdmi *intel_hdmi = intel_attached_hdmi(connector);
 
 		hdmi_to_dig_port(intel_hdmi)->base.type = INTEL_OUTPUT_HDMI;
@@ -1521,7 +1498,7 @@ intel_hdmi_force(struct drm_connector *connector)
 	if (connector->status != connector_status_connected)
 		return;
 
-	intel_hdmi_set_edid(connector, true);
+	intel_hdmi_set_edid(connector);
 	hdmi_to_dig_port(intel_hdmi)->base.type = INTEL_OUTPUT_HDMI;
 }
 
-- 
2.1.4



-- 
Jani Nikula, Intel Open Source Technology Center

[toc] | [prev] | [next] | [standalone]

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

FromMartin Steigerwald <martin@lichtvoll.de>
Date2016-09-15 17:40 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shGVz-ku-9@gated-at.bofh.it>
In reply to#1483198
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.

-- 
Martin

[toc] | [prev] | [next] | [standalone]

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

FromJani Nikula <jani.nikula@linux.intel.com>
Date2016-09-16 09:00 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shVhU-18a-5@gated-at.bofh.it>
In reply to#1484328
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

[toc] | [prev] | [next] | [standalone]

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

FromMartin Steigerwald <martin@lichtvoll.de>
Date2016-09-14 13:40 +0200
SubjectRe: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shgHL-gO-11@gated-at.bofh.it>
In reply to#1483119
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

[toc] | [prev] | [next] | [standalone]

#1483167 — Re: [Intel-gfx] 4.8-rc1: it is now common that machine needs re-run of xrandr after resume

FromChris Wilson <chris@chris-wilson.co.uk>
Date2016-09-14 12:40 +0200
SubjectRe: [Intel-gfx] 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
Message-ID<shfLI-89J-37@gated-at.bofh.it>
In reply to#1482755
On Tue, Sep 13, 2016 at 11:04:37PM +0200, Pavel Machek wrote:
> Hi!
> 
> > I have
> > 
> > 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
> > Integrated Graphics Controller (rev 03)
> > 
> > In previous kernels, resume worked ok. With 4.8-rc1, I quite often (1
> > in 10 resumes?) get in state where primary monitor (DVI) is dead (in
> > powersave) and all windows move to secondary monitor (VGA). Running
> > "xrandr" fixes that.
> > 
> > I'll update to newer rc and see if it happens again, but if you have
> > any ideas, now would be good time.
> 
> Ok. With -rc6, X are completely broken. I got notification "could not
> restore CRTC config for screen 63" or something like that, and window
> manager just does not start.
> 
> X log is attached as delme, kernel log as delme2. Nothing too
> suspicious :-(.

[   234.547] (EE) intel(0): failed to set mode: Permission denied
upon resume.

There is a VT switch so there should be a DropMaster, SetMaster combo
across resume, but that didn't flag any errors. I couldn't see any sign
of logind (so no revocation), so just some breakage in the setmaster
reauthentication?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web