* 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-13 20:23 Pavel Machek
2016-09-13 20:38 ` Martin Steigerwald
2016-09-13 21:04 ` Pavel Machek
0 siblings, 2 replies; 24+ messages in thread
From: Pavel Machek @ 2016-09-13 20:23 UTC (permalink / raw)
To: kernel list, daniel.vetter, jani.nikula, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
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 21:04 ` Pavel Machek
1 sibling, 0 replies; 24+ messages in thread
From: Martin Steigerwald @ 2016-09-13 20:38 UTC (permalink / raw)
To: Pavel Machek
Cc: kernel list, daniel.vetter, jani.nikula, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-13 20:38 ` Martin Steigerwald
0 siblings, 0 replies; 24+ messages in thread
From: Martin Steigerwald @ 2016-09-13 20:38 UTC (permalink / raw)
To: Pavel Machek
Cc: intel-gfx, Rafael J. Wysocki, kernel list, dri-devel, daniel.vetter
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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
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 21:04 ` Pavel Machek
2016-09-14 7:38 ` Jani Nikula
2016-09-14 10:33 ` [Intel-gfx] " Chris Wilson
1 sibling, 2 replies; 24+ messages in thread
From: Pavel Machek @ 2016-09-13 21:04 UTC (permalink / raw)
To: kernel list, daniel.vetter, jani.nikula, intel-gfx, dri-devel,
Rafael J. Wysocki
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
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 :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: delme --]
[-- Type: text/plain, Size: 30818 bytes --]
[ 227.978]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[ 227.978] X Protocol Version 11, Revision 0
[ 227.978] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
[ 227.978] Current Operating System: Linux amd 4.8.0-rc6 #59 SMP Tue Sep 13 22:55:13 CEST 2016 x86_64
[ 227.978] Kernel command line: BOOT_IMAGE=(hd0,2)/l/linux-64/arch/x86/boot/bzImage root=PARTUUID=bdb19d30-04 resume=PARTUUID=bdb19d30-01
[ 227.978] Build Date: 11 February 2015 01:14:26AM
[ 227.978] xorg-server 2:1.16.4-1 (http://www.debian.org/support)
[ 227.978] Current version of pixman: 0.32.6
[ 227.979] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 227.979] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 227.979] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 13 23:01:42 2016
[ 227.979] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 227.979] (==) No Layout section. Using the first Screen section.
[ 227.979] (==) No screen section available. Using defaults.
[ 227.979] (**) |-->Screen "Default Screen Section" (0)
[ 227.979] (**) | |-->Monitor "<default monitor>"
[ 227.979] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 227.979] (==) Automatically adding devices
[ 227.979] (==) Automatically enabling devices
[ 227.979] (==) Automatically adding GPU devices
[ 227.979] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 227.979] Entry deleted from font path.
[ 227.980] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 227.980] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 227.980] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 227.980] (II) Loader magic: 0x5683b700
[ 227.980] (II) Module ABI versions:
[ 227.980] X.Org ANSI C Emulation: 0.4
[ 227.980] X.Org Video Driver: 18.0
[ 227.980] X.Org XInput driver : 21.0
[ 227.980] X.Org Server Extension : 8.0
[ 227.980] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 227.995] (--) PCI:*(0:0:2:0) 8086:2e32:8086:d614 rev 3, Mem @ 0xd0000000/4194304, 0xc0000000/268435456, I/O @ 0x0000f140/8, BIOS @ 0x????????/131072
[ 227.995] (--) PCI: (0:0:2:1) 8086:2e33:8086:d614 rev 3, Mem @ 0xd0400000/1048576
[ 227.995] (II) LoadModule: "glx"
[ 227.997] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 227.999] (II) Module glx: vendor="X.Org Foundation"
[ 227.999] compiled for 1.16.4, module version = 1.0.0
[ 227.999] ABI class: X.Org Server Extension, version 8.0
[ 227.999] (==) AIGLX enabled
[ 227.999] (==) Matched intel as autoconfigured driver 0
[ 227.999] (==) Matched intel as autoconfigured driver 1
[ 227.999] (==) Matched modesetting as autoconfigured driver 2
[ 227.999] (==) Matched fbdev as autoconfigured driver 3
[ 227.999] (==) Matched vesa as autoconfigured driver 4
[ 227.999] (==) Assigned the driver to the xf86ConfigLayout
[ 227.999] (II) LoadModule: "intel"
[ 227.999] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 228.000] (II) Module intel: vendor="X.Org Foundation"
[ 228.000] compiled for 1.15.99.904, module version = 2.21.15
[ 228.000] Module class: X.Org Video Driver
[ 228.000] ABI class: X.Org Video Driver, version 18.0
[ 228.000] (II) LoadModule: "modesetting"
[ 228.000] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 228.001] (II) Module modesetting: vendor="X.Org Foundation"
[ 228.001] compiled for 1.16.4, module version = 0.9.0
[ 228.001] Module class: X.Org Video Driver
[ 228.001] ABI class: X.Org Video Driver, version 18.0
[ 228.001] (II) LoadModule: "fbdev"
[ 228.001] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 228.001] (II) Module fbdev: vendor="X.Org Foundation"
[ 228.001] compiled for 1.15.99.904, module version = 0.4.4
[ 228.001] Module class: X.Org Video Driver
[ 228.002] ABI class: X.Org Video Driver, version 18.0
[ 228.002] (II) LoadModule: "vesa"
[ 228.002] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 228.002] (II) Module vesa: vendor="X.Org Foundation"
[ 228.002] compiled for 1.15.99.904, module version = 2.3.3
[ 228.002] Module class: X.Org Video Driver
[ 228.002] ABI class: X.Org Video Driver, version 18.0
[ 228.003] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
[ 228.004] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 228.004] (II) FBDEV: driver for framebuffer: fbdev
[ 228.004] (II) VESA: driver for VESA chipsets: vesa
[ 228.004] (++) using VT number 7
[ 228.041] (WW) Falling back to old probe method for modesetting
[ 228.057] (WW) Falling back to old probe method for fbdev
[ 228.057] (II) Loading sub module "fbdevhw"
[ 228.057] (II) LoadModule: "fbdevhw"
[ 228.058] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 228.058] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 228.058] compiled for 1.16.4, module version = 0.0.2
[ 228.058] ABI class: X.Org Video Driver, version 18.0
[ 228.058] (WW) Falling back to old probe method for vesa
[ 228.074] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 228.074] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 228.074] (==) intel(0): RGB weight 888
[ 228.074] (==) intel(0): Default visual is TrueColor
[ 228.074] (--) intel(0): Integrated Graphics Chipset: Intel(R) G41
[ 228.074] (**) intel(0): Relaxed fencing enabled
[ 228.074] (**) intel(0): Wait on SwapBuffers? enabled
[ 228.074] (**) intel(0): Triple buffering? enabled
[ 228.074] (**) intel(0): Framebuffer tiled
[ 228.074] (**) intel(0): Pixmaps tiled
[ 228.075] (**) intel(0): 3D buffers tiled
[ 228.075] (**) intel(0): SwapBuffers wait enabled
[ 228.075] (==) intel(0): video overlay key set to 0x101fe
[ 228.252] (II) intel(0): Output VGA1 has no monitor section
[ 228.572] (II) intel(0): Output HDMI1 has no monitor section
[ 228.572] (II) intel(0): Output DP1 has no monitor section
[ 228.736] (II) intel(0): EDID for output VGA1
[ 228.736] (II) intel(0): Manufacturer: DEL Model: a013 Serial#: 926494805
[ 228.736] (II) intel(0): Year: 2005 Week: 46
[ 228.736] (II) intel(0): EDID Version: 1.3
[ 228.736] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 228.736] (II) intel(0): Sync: Separate
[ 228.736] (II) intel(0): Max Image Size [cm]: horiz.: 30 vert.: 23
[ 228.736] (II) intel(0): Gamma: 2.20
[ 228.736] (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 228.736] (II) intel(0): Default color space is primary color space
[ 228.736] (II) intel(0): First detailed timing is preferred mode
[ 228.736] (II) intel(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 228.736] (II) intel(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
[ 228.736] (II) intel(0): Supported established timings:
[ 228.736] (II) intel(0): 720x400@70Hz
[ 228.736] (II) intel(0): 640x480@60Hz
[ 228.736] (II) intel(0): 640x480@75Hz
[ 228.736] (II) intel(0): 800x600@60Hz
[ 228.736] (II) intel(0): 800x600@75Hz
[ 228.736] (II) intel(0): 1024x768@60Hz
[ 228.736] (II) intel(0): 1024x768@75Hz
[ 228.736] (II) intel(0): Manufacturer's mask: 0
[ 228.736] (II) intel(0): Supported detailed timing:
[ 228.736] (II) intel(0): clock: 65.0 MHz Image Size: 304 x 228 mm
[ 228.736] (II) intel(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1344 h_border: 0
[ 228.736] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0
[ 228.737] (II) intel(0): Serial No: JC1415B7790U
[ 228.737] (II) intel(0): Monitor name: DELL E156FP
[ 228.737] (II) intel(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 61 kHz, PixClock max 85 MHz
[ 228.737] (II) intel(0): EDID (in hex):
[ 228.737] (II) intel(0): 00ffffffffffff0010ac13a055303937
[ 228.737] (II) intel(0): 2e0f0103681e1778eeee91a3544c9926
[ 228.737] (II) intel(0): 0f5054a54a0001010101010101010101
[ 228.737] (II) intel(0): 01010101010164190040410026301888
[ 228.737] (II) intel(0): 360030e410000018000000ff004a4331
[ 228.737] (II) intel(0): 3431354237373930550a000000fc0044
[ 228.737] (II) intel(0): 454c4c204531353646500a20000000fd
[ 228.737] (II) intel(0): 00384b1e3d08000a202020202020006b
[ 228.737] (II) intel(0): Printing probed modes for output VGA1
[ 228.737] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz eP)
[ 228.737] (II) intel(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 228.737] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 228.737] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 228.737] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 228.737] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 228.737] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 229.056] (II) intel(0): EDID for output HDMI1
[ 229.056] (II) intel(0): Manufacturer: FUS Model: 80a Serial#: 5875
[ 229.056] (II) intel(0): Year: 2011 Week: 21
[ 229.056] (II) intel(0): EDID Version: 1.3
[ 229.056] (II) intel(0): Digital Display Input
[ 229.056] (II) intel(0): Max Image Size [cm]: horiz.: 48 vert.: 27
[ 229.056] (II) intel(0): Gamma: 2.20
[ 229.056] (II) intel(0): DPMS capabilities: Off
[ 229.056] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 229.056] (II) intel(0): First detailed timing is preferred mode
[ 229.056] (II) intel(0): redX: 0.637 redY: 0.330 greenX: 0.316 greenY: 0.620
[ 229.056] (II) intel(0): blueX: 0.153 blueY: 0.067 whiteX: 0.313 whiteY: 0.329
[ 229.056] (II) intel(0): Supported established timings:
[ 229.056] (II) intel(0): 720x400@70Hz
[ 229.056] (II) intel(0): 640x480@60Hz
[ 229.056] (II) intel(0): 640x480@75Hz
[ 229.056] (II) intel(0): 800x600@60Hz
[ 229.056] (II) intel(0): 800x600@75Hz
[ 229.056] (II) intel(0): 1024x768@60Hz
[ 229.056] (II) intel(0): 1024x768@75Hz
[ 229.056] (II) intel(0): 1280x1024@75Hz
[ 229.056] (II) intel(0): Manufacturer's mask: 0
[ 229.056] (II) intel(0): Supported standard timings:
[ 229.056] (II) intel(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 229.056] (II) intel(0): #1: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 229.056] (II) intel(0): #2: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 229.056] (II) intel(0): #3: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 229.056] (II) intel(0): Supported detailed timing:
[ 229.056] (II) intel(0): clock: 148.5 MHz Image Size: 478 x 268 mm
[ 229.057] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 229.057] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 229.057] (II) intel(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 82 kHz, PixClock max 165 MHz
[ 229.057] (II) intel(0): Monitor name: L22T-3 LED
[ 229.057] (II) intel(0): Serial No: YV5F005875
[ 229.057] (II) intel(0): EDID (in hex):
[ 229.057] (II) intel(0): 00ffffffffffff001ab30a08f3160000
[ 229.057] (II) intel(0): 1515010380301b782a2355a354519e27
[ 229.057] (II) intel(0): 115054a54b008180a9409500b3000101
[ 229.057] (II) intel(0): 010101010101023a801871382d40582c
[ 229.057] (II) intel(0): 4500de0c1100001e000000fd00384c1e
[ 229.057] (II) intel(0): 5210000a202020202020000000fc004c
[ 229.057] (II) intel(0): 3232542d33204c45440a2020000000ff
[ 229.057] (II) intel(0): 00595635463030353837350a2020003d
[ 229.057] (II) intel(0): Printing probed modes for output HDMI1
[ 229.057] (II) intel(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 229.057] (II) intel(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 229.057] (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 229.057] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 229.057] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 229.057] (II) intel(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 229.057] (II) intel(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 229.057] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 229.057] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 229.057] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 229.057] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 229.057] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 229.057] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 229.057] (II) intel(0): EDID for output DP1
[ 229.057] (II) intel(0): Output VGA1 connected
[ 229.057] (II) intel(0): Output HDMI1 connected
[ 229.058] (II) intel(0): Output DP1 disconnected
[ 229.058] (II) intel(0): Using exact sizes for initial modes
[ 229.058] (II) intel(0): Output VGA1 using initial mode 1024x768
[ 229.058] (II) intel(0): Output HDMI1 using initial mode 1024x768
[ 229.058] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 229.058] (II) intel(0): Kernel page flipping support detected, enabling
[ 229.058] (==) intel(0): DPI set to (96, 96)
[ 229.058] (II) Loading sub module "fb"
[ 229.058] (II) LoadModule: "fb"
[ 229.058] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 229.058] (II) Module fb: vendor="X.Org Foundation"
[ 229.058] compiled for 1.16.4, module version = 1.0.0
[ 229.058] ABI class: X.Org ANSI C Emulation, version 0.4
[ 229.058] (II) Loading sub module "dri2"
[ 229.058] (II) LoadModule: "dri2"
[ 229.058] (II) Module "dri2" already built-in
[ 229.058] (II) UnloadModule: "modesetting"
[ 229.059] (II) Unloading modesetting
[ 229.059] (II) UnloadModule: "fbdev"
[ 229.059] (II) Unloading fbdev
[ 229.059] (II) UnloadSubModule: "fbdevhw"
[ 229.059] (II) Unloading fbdevhw
[ 229.059] (II) UnloadModule: "vesa"
[ 229.059] (II) Unloading vesa
[ 229.059] (==) Depth 24 pixmap format is 32 bpp
[ 229.059] (II) intel(0): [DRI2] Setup complete
[ 229.059] (II) intel(0): [DRI2] DRI driver: i965
[ 229.059] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled
[ 229.078] (II) UXA(0): Driver registered support for the following operations:
[ 229.078] (II) solid
[ 229.078] (II) copy
[ 229.078] (II) composite (RENDER acceleration)
[ 229.078] (II) put_image
[ 229.078] (II) get_image
[ 229.078] (==) intel(0): Backing store enabled
[ 229.078] (==) intel(0): Silken mouse enabled
[ 229.078] (II) intel(0): Initializing HW Cursor
[ 229.078] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 229.125] (==) intel(0): DPMS enabled
[ 229.125] (==) intel(0): Intel XvMC decoder enabled
[ 229.125] (II) intel(0): Set up textured video
[ 229.125] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 229.125] (II) intel(0): direct rendering: DRI2 Enabled
[ 229.125] (==) intel(0): hotplug detection: "enabled"
[ 229.229] (--) RandR disabled
[ 229.241] (II) SELinux: Disabled on system
[ 229.247] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 229.247] (II) AIGLX: enabled GLX_ARB_create_context
[ 229.247] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 229.247] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 229.247] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 229.247] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 229.247] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 229.247] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 229.247] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 229.247] (II) AIGLX: Loaded and initialized i965
[ 229.247] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 229.248] (II) intel(0): Setting screen physical size to 270 x 203
[ 229.287] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 229.287] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 229.287] (II) LoadModule: "evdev"
[ 229.288] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 229.288] (II) Module evdev: vendor="X.Org Foundation"
[ 229.288] compiled for 1.16.0, module version = 2.9.0
[ 229.288] Module class: X.Org XInput Driver
[ 229.288] ABI class: X.Org XInput driver, version 21.0
[ 229.288] (II) Using input driver 'evdev' for 'Power Button'
[ 229.288] (**) Power Button: always reports core events
[ 229.288] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 229.288] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 229.288] (--) evdev: Power Button: Found keys
[ 229.288] (II) evdev: Power Button: Configuring as keyboard
[ 229.288] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 229.288] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 229.288] (**) Option "xkb_rules" "evdev"
[ 229.288] (**) Option "xkb_model" "pc105"
[ 229.289] (**) Option "xkb_layout" "us"
[ 229.290] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
[ 229.290] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 229.290] (II) Using input driver 'evdev' for 'Video Bus'
[ 229.290] (**) Video Bus: always reports core events
[ 229.290] (**) evdev: Video Bus: Device: "/dev/input/event2"
[ 229.290] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 229.290] (--) evdev: Video Bus: Found keys
[ 229.290] (II) evdev: Video Bus: Configuring as keyboard
[ 229.290] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input2/event2"
[ 229.290] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 229.290] (**) Option "xkb_rules" "evdev"
[ 229.290] (**) Option "xkb_model" "pc105"
[ 229.290] (**) Option "xkb_layout" "us"
[ 229.291] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 229.291] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 229.291] (II) Using input driver 'evdev' for 'Power Button'
[ 229.291] (**) Power Button: always reports core events
[ 229.291] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 229.291] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 229.291] (--) evdev: Power Button: Found keys
[ 229.291] (II) evdev: Power Button: Configuring as keyboard
[ 229.291] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[ 229.291] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 229.291] (**) Option "xkb_rules" "evdev"
[ 229.291] (**) Option "xkb_model" "pc105"
[ 229.291] (**) Option "xkb_layout" "us"
[ 229.293] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event4)
[ 229.293] (II) No input driver specified, ignoring this device.
[ 229.293] (II) This device may have been added with another device file.
[ 229.293] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event5)
[ 229.293] (II) No input driver specified, ignoring this device.
[ 229.293] (II) This device may have been added with another device file.
[ 229.294] (II) config/udev: Adding input device HDA Intel Line Out (/dev/input/event6)
[ 229.294] (II) No input driver specified, ignoring this device.
[ 229.294] (II) This device may have been added with another device file.
[ 229.295] (II) config/udev: Adding input device Chicony USB Keyboard (/dev/input/event7)
[ 229.295] (**) Chicony USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 229.295] (II) Using input driver 'evdev' for 'Chicony USB Keyboard'
[ 229.295] (**) Chicony USB Keyboard: always reports core events
[ 229.295] (**) evdev: Chicony USB Keyboard: Device: "/dev/input/event7"
[ 229.295] (--) evdev: Chicony USB Keyboard: Vendor 0x4f2 Product 0x111
[ 229.295] (--) evdev: Chicony USB Keyboard: Found keys
[ 229.295] (II) evdev: Chicony USB Keyboard: Configuring as keyboard
[ 229.295] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7.1/1-7.1.1/1-7.1.1:1.0/0003:04F2:0111.0001/input/input10/event7"
[ 229.295] (II) XINPUT: Adding extended input device "Chicony USB Keyboard" (type: KEYBOARD, id 9)
[ 229.295] (**) Option "xkb_rules" "evdev"
[ 229.295] (**) Option "xkb_model" "pc105"
[ 229.295] (**) Option "xkb_layout" "us"
[ 229.297] (II) config/udev: Adding input device Chicony USB Keyboard (/dev/input/event8)
[ 229.297] (**) Chicony USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 229.297] (II) Using input driver 'evdev' for 'Chicony USB Keyboard'
[ 229.297] (**) Chicony USB Keyboard: always reports core events
[ 229.297] (**) evdev: Chicony USB Keyboard: Device: "/dev/input/event8"
[ 229.297] (--) evdev: Chicony USB Keyboard: Vendor 0x4f2 Product 0x111
[ 229.297] (--) evdev: Chicony USB Keyboard: Found keys
[ 229.297] (II) evdev: Chicony USB Keyboard: Configuring as keyboard
[ 229.297] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7.1/1-7.1.1/1-7.1.1:1.1/0003:04F2:0111.0002/input/input11/event8"
[ 229.297] (II) XINPUT: Adding extended input device "Chicony USB Keyboard" (type: KEYBOARD, id 10)
[ 229.297] (**) Option "xkb_rules" "evdev"
[ 229.297] (**) Option "xkb_model" "pc105"
[ 229.297] (**) Option "xkb_layout" "us"
[ 229.298] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event9)
[ 229.298] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 229.298] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
[ 229.298] (**) Logitech USB Optical Mouse: always reports core events
[ 229.298] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event9"
[ 229.298] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
[ 229.298] (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
[ 229.298] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
[ 229.298] (--) evdev: Logitech USB Optical Mouse: Found relative axes
[ 229.298] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
[ 229.298] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
[ 229.298] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
[ 229.298] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
[ 229.299] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 229.299] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7.1/1-7.1.2/1-7.1.2:1.0/0003:046D:C05A.0003/input/input12/event9"
[ 229.299] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 11)
[ 229.299] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
[ 229.299] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
[ 229.299] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
[ 229.299] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
[ 229.299] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
[ 229.300] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
[ 229.300] (II) No input driver specified, ignoring this device.
[ 229.300] (II) This device may have been added with another device file.
[ 229.301] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 229.301] (II) No input driver specified, ignoring this device.
[ 229.301] (II) This device may have been added with another device file.
[ 231.508] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 232.562] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 232.836] (II) intel(0): EDID vendor "DEL", prod id 40979
[ 232.836] (II) intel(0): Using EDID range info for horizontal sync
[ 232.836] (II) intel(0): Using EDID range info for vertical refresh
[ 232.836] (II) intel(0): Printing DDC gathered Modelines:
[ 232.836] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz eP)
[ 232.836] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 232.836] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 232.836] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 232.836] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 232.836] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 232.836] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 233.472] (II) intel(0): EDID vendor "DEL", prod id 40979
[ 233.472] (II) intel(0): Using hsync ranges from config file
[ 233.472] (II) intel(0): Using vrefresh ranges from config file
[ 233.472] (II) intel(0): Printing DDC gathered Modelines:
[ 233.472] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz eP)
[ 233.472] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 233.472] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 233.472] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 233.472] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 233.472] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 233.472] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 233.976] (II) intel(0): EDID vendor "DEL", prod id 40979
[ 233.976] (II) intel(0): Using hsync ranges from config file
[ 233.976] (II) intel(0): Using vrefresh ranges from config file
[ 233.976] (II) intel(0): Printing DDC gathered Modelines:
[ 233.976] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz eP)
[ 233.976] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 233.976] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 233.976] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 233.976] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 233.976] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 233.976] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 234.452] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 234.547] (II) intel(0): Allocated new frame buffer 1920x1848 stride 7680, tiled
[ 234.547] (EE) intel(0): failed to set mode: Permission denied
[ 235.093] (II) intel(0): Allocated new frame buffer 1920x1848 stride 7680, tiled
[ 235.093] (EE) intel(0): failed to set mode: Permission denied
[ 237.189] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 237.444] (II) intel(0): EDID vendor "DEL", prod id 40979
[ 237.444] (II) intel(0): Using hsync ranges from config file
[ 237.444] (II) intel(0): Using vrefresh ranges from config file
[ 237.444] (II) intel(0): Printing DDC gathered Modelines:
[ 237.444] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz eP)
[ 237.444] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 237.444] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 237.444] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 237.444] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 237.444] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 237.444] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 252.652] (II) AIGLX: Suspending AIGLX clients for VT switch
[-- Attachment #3: delme2.gz --]
[-- Type: application/gzip, Size: 15122 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-13 21:04 ` Pavel Machek
@ 2016-09-14 7:38 ` Jani Nikula
2016-09-14 10:33 ` [Intel-gfx] " Chris Wilson
1 sibling, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 7:38 UTC (permalink / raw)
To: Pavel Machek, kernel list, daniel.vetter, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-14 7:38 ` Jani Nikula
0 siblings, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 7:38 UTC (permalink / raw)
To: Pavel Machek, kernel list, daniel.vetter, intel-gfx, dri-devel,
Rafael J. Wysocki
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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-13 20:38 ` Martin Steigerwald
@ 2016-09-14 7:43 ` Pavel Machek
-1 siblings, 0 replies; 24+ messages in thread
From: Pavel Machek @ 2016-09-14 7:43 UTC (permalink / raw)
To: Martin Steigerwald
Cc: kernel list, daniel.vetter, jani.nikula, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-14 7:43 ` Pavel Machek
0 siblings, 0 replies; 24+ messages in thread
From: Pavel Machek @ 2016-09-14 7:43 UTC (permalink / raw)
To: Martin Steigerwald
Cc: intel-gfx, Rafael J. Wysocki, kernel list, dri-devel, daniel.vetter
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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-14 7:38 ` Jani Nikula
@ 2016-09-14 7:45 ` Jani Nikula
-1 siblings, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 7:45 UTC (permalink / raw)
To: Pavel Machek, kernel list, daniel.vetter, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-14 7:45 ` Jani Nikula
0 siblings, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 7:45 UTC (permalink / raw)
To: Pavel Machek, kernel list, daniel.vetter, intel-gfx, dri-devel,
Rafael J. Wysocki
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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-14 7:38 ` Jani Nikula
@ 2016-09-14 7:54 ` Pavel Machek
-1 siblings, 0 replies; 24+ messages in thread
From: Pavel Machek @ 2016-09-14 7:54 UTC (permalink / raw)
To: Jani Nikula
Cc: kernel list, daniel.vetter, intel-gfx, dri-devel, Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-14 7:54 ` Pavel Machek
0 siblings, 0 replies; 24+ messages in thread
From: Pavel Machek @ 2016-09-14 7:54 UTC (permalink / raw)
To: Jani Nikula
Cc: daniel.vetter, intel-gfx, Rafael J. Wysocki, kernel list, dri-devel
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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
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:32 ` Martin Steigerwald
-1 siblings, 2 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 9:17 UTC (permalink / raw)
To: Pavel Machek, Martin Steigerwald
Cc: kernel list, daniel.vetter, intel-gfx, dri-devel, Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-14 7:43 ` Pavel Machek
(?)
@ 2016-09-14 10:03 ` Jani Nikula
-1 siblings, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 10:03 UTC (permalink / raw)
To: Pavel Machek, Martin Steigerwald
Cc: kernel list, daniel.vetter, intel-gfx, dri-devel, Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Intel-gfx] 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-13 21:04 ` Pavel Machek
2016-09-14 7:38 ` Jani Nikula
@ 2016-09-14 10:33 ` Chris Wilson
1 sibling, 0 replies; 24+ messages in thread
From: Chris Wilson @ 2016-09-14 10:33 UTC (permalink / raw)
To: Pavel Machek
Cc: kernel list, daniel.vetter, jani.nikula, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-14 9:17 ` Jani Nikula
@ 2016-09-14 11:14 ` Jani Nikula
2016-09-14 11:32 ` Martin Steigerwald
1 sibling, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 11:14 UTC (permalink / raw)
To: Pavel Machek, Martin Steigerwald
Cc: kernel list, daniel.vetter, intel-gfx, dri-devel, Rafael J. Wysocki
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
^ permalink raw reply related [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-14 11:14 ` Jani Nikula
0 siblings, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-14 11:14 UTC (permalink / raw)
To: Pavel Machek, Martin Steigerwald
Cc: daniel.vetter, intel-gfx, Rafael J. Wysocki, kernel list, dri-devel
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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-14 9:17 ` Jani Nikula
@ 2016-09-14 11:32 ` Martin Steigerwald
2016-09-14 11:32 ` Martin Steigerwald
1 sibling, 0 replies; 24+ messages in thread
From: Martin Steigerwald @ 2016-09-14 11:32 UTC (permalink / raw)
To: Jani Nikula
Cc: Pavel Machek, kernel list, daniel.vetter, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-14 11:32 ` Martin Steigerwald
0 siblings, 0 replies; 24+ messages in thread
From: Martin Steigerwald @ 2016-09-14 11:32 UTC (permalink / raw)
To: Jani Nikula
Cc: intel-gfx, Rafael J. Wysocki, kernel list, dri-devel,
Pavel Machek, daniel.vetter
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-14 11:14 ` Jani Nikula
@ 2016-09-15 15:34 ` Martin Steigerwald
-1 siblings, 0 replies; 24+ messages in thread
From: Martin Steigerwald @ 2016-09-15 15:34 UTC (permalink / raw)
To: Jani Nikula
Cc: Pavel Machek, kernel list, daniel.vetter, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-09-15 15:34 ` Martin Steigerwald
0 siblings, 0 replies; 24+ messages in thread
From: Martin Steigerwald @ 2016-09-15 15:34 UTC (permalink / raw)
To: Jani Nikula
Cc: intel-gfx, Rafael J. Wysocki, kernel list, dri-devel,
Pavel Machek, daniel.vetter
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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-15 15:34 ` Martin Steigerwald
(?)
@ 2016-09-16 6:57 ` Jani Nikula
-1 siblings, 0 replies; 24+ messages in thread
From: Jani Nikula @ 2016-09-16 6:57 UTC (permalink / raw)
To: Martin Steigerwald
Cc: Pavel Machek, kernel list, daniel.vetter, intel-gfx, dri-devel,
Rafael J. Wysocki
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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
2016-09-14 11:14 ` Jani Nikula
@ 2016-10-18 14:13 ` Pavel Machek
-1 siblings, 0 replies; 24+ messages in thread
From: Pavel Machek @ 2016-10-18 14:13 UTC (permalink / raw)
To: Jani Nikula
Cc: Martin Steigerwald, kernel list, daniel.vetter, intel-gfx,
dri-devel, Rafael J. Wysocki
[-- Attachment #1: Type: text/plain, Size: 4256 bytes --]
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: 4.8-rc1: it is now common that machine needs re-run of xrandr after resume
@ 2016-10-18 14:13 ` Pavel Machek
0 siblings, 0 replies; 24+ messages in thread
From: Pavel Machek @ 2016-10-18 14:13 UTC (permalink / raw)
To: Jani Nikula
Cc: Martin Steigerwald, intel-gfx, Rafael J. Wysocki, kernel list,
dri-devel, daniel.vetter
[-- Attachment #1.1: Type: text/plain, Size: 4256 bytes --]
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
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2016-10-18 14:13 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2016-09-14 11:32 ` Martin Steigerwald
2016-09-14 10:33 ` [Intel-gfx] " Chris Wilson
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.