Created attachment 109941 [details] xorg _log There are odd black/blank/gray screen issues that are occurring with the intel-drm driver in the 3.11.1 kernel. Sometimes, on a cold-boot the login manager (gdm3 in this case) will properly show but after entering credentials the screen will either produce a black screen or gray screen with thick black lines. This will happen 50% of the time. About 10% of the time switching to a virtual terminal and back will fix the issue and display the desktop as expected. This also happens randomly after a suspend/resume cycle. Xorg log attached and it appears clean, the log does not differ when the bug happens. I am not passing any relevant kernel parameters at boot but when using the nomodeset option, there are no issues present. 3.12 RC2 kernel was compiled and the issue is still present. inxi -Gx: Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller bus-ID:00:02.0 X.Org: 1.14.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@59.9hz GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 9.2.0 Direct Rendering: Yes lscpi: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Device 0a0c (rev 09) 00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 (rev e4) 00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04) 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) There is no deprecated xorg.conf file in use. I really wasn't too sure what else is needed for this bug report, please let me know if additional information is needed and I will provide it promptly.
I'm attaching a new xorg, the issue just happened after a logout and an attempted login. I switched to VT1 and back and was able to resume without a reboot.
Created attachment 109951 [details] new_xorg
Update xf86-video-intel for a workaround.
Chris, I pulled the driver last night and compiled. Issue is still present.
The last logfile is still an old driver from before the Haswell w/a I was thinking of. However, I mistook your 3200 pixel wide eDP for an extended desktop and so the issue is not the same one anyway.
Chris, I had downloaded the source tar from the Intel graphics Q3 bundle with a -903 release. I'll pull from git anyway so I'm running any fixes not included in it. You are correct, the laptop screen is a 3200x1800 pixel screen--which surprisingly works at that or lesser resolutions.
Created attachment 109961 [details] xorg_latest_driver I've updated the xf86-video-intel driver. Same issue, just resumed and had a blank screen--forced to reboot. Here is the updated Xorg log. Is there anything else I can provide?
Please add drm.debug=0xe module parameter, and provide dmesg from boot to the issue. If it usually takes a long time, you may need to increase log_buf_size. Let's see if there's anything of interest there.
Do you still see this issue with latest drm-intel-nightly from http://cgit.freedesktop.org/~danvet/drm-intel/log/?h=drm-intel-nightly and latest xf86-video-intel from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ Could you please provide new xorg log and also the info requested by Jani: dmesg with kernel booted with drm.debug=0xe.
Hi there, It's been a while with no input. Feel free to reopen it with proper logs at any time if you are still facing the issue. Thanks, Rodrigo.