[Bug 99610] New: NUC6i5SYB Linux screen blanks 2 seconds during use (displayport only?)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jan 31 04:50:45 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=99610
Bug ID: 99610
Summary: NUC6i5SYB Linux screen blanks 2 seconds during use
(displayport only?)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: grantgrundler at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 129243
--> https://bugs.freedesktop.org/attachment.cgi?id=129243&action=edit
X log since starting the X server - includes episodes of blanking due to
openarena and google maps (under chrome)
As Paulo requested on https://bugs.freedesktop.org/show_bug.cgi?id=94605, I'm
opening a new bug to help collect information about the "screen blanking 2
seconds" when NUC6i5SYB connected via displayport to a monitor.
I'm sorry that I didn't see Eero Tamminen's (2016-08-22 14:30:37 UTC comment
#49) comment until now:
> This sounds more like the X issues with DRI3 than kernel issue.
> Could you try both Intel DDX &modesetting X drivers and with
> Intel DDX both DRI3 and DRI2?
Yes, I certainly can. But I need specific instructions on where to get the
binaries or how to compile and install them locally. I'll try to follow the
"HOW TO FILE A BUG REPORT" instructions linked in the "component description"
field.
I do NOT see an "i915 platform" information field (as described by the HOW-TO).
> If it's indeed X issue, please file separate bug about it.
I believe he is correct. Last year I reverted to older kernels (4.1 and 4.0)
that did not previously exhibit this symptom and the symptom persisted. I
believe this issue is rooted in user space and might be related to the display
port output.
I'll also note that my NUC died late last year and was replaced under warranty
by Intel (while there were issues with the return instructions and it took 6+
weeks to resolve everything, it was taken care of - kudos to Intel support for
their honest help with this). I'm reproducing the issue with the brand spank'n
new HW just as frequently.
I do not see any GPU hangs, FIFO overruns, or other symptoms in my dmesg or
/var/log/messages output.
I don't recall exactly when this symptom started but it was NOT occurring when
I first purchased and used the NUC6i5SYB in Feb and March, 2016. I believe it
started after May, 2016 (ie showed up in Debian testing - so bug could have
been introduced earlier into dev source tree).
How to reproduce:
1) run openarena in 2560x1440
2) chrome browser: zoom/pan in Google maps when in "earth" mode (and HW accel
is enabled)
[262565.324] (==) ModulePath set to "/usr/lib/xorg/modules"
[262565.324] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[262565.324] (II) Loader magic: 0x55ac0d3d0e00
[262565.324] (II) Module ABI versions:
[262565.324] X.Org ANSI C Emulation: 0.4
[262565.324] X.Org Video Driver: 23.0
[262565.324] X.Org XInput driver : 24.1
[262565.324] X.Org Server Extension : 10.0
[262565.325] (++) using VT number 7
...
[262565.325] (II) xfree86: Adding drm device (/dev/dri/card0)
[262565.337] (--) PCI:*(0:0:2:0) 8086:1926:8086:2063 rev 10, Mem @
0xde000000/16777216, 0xc0000000/268435456, I/O @ 0x0000f000/64, BIOS @
0x????????/131072
(and I've attached the /var/log/Xorg.0.log from this sign in session)
The monitor in my case is Samsung U28D590D (28", 4J UHD):
http://www.samsung.com/levant/consumer/it/monitor/uhd-monitor/LU28D590DS/ZN/
The NUC is connected via mini-displayport since AFAIK, displayport is the only
link that will support 4K output.
I will test with HDMI port (at a lower resolution) and report later (since i'm
afraid switching video input might crash or force restarting graphics server).
I'm running Debian "testing" (freshly updated)
Linux gggnuc6 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64 GNU/Linux
I will add "drm.debug=0x1e log_buf_len=1M" and attach the dmesg buffer once I
have that.
# dpkg -l | fgrep -i drm
ii libdrm-amdgpu1:amd64 2.4.74-1
amd64 Userspace interface to amdgpu-specific kernel DRM services --
runtime
ii libdrm-intel1:amd64 2.4.74-1
amd64 Userspace interface to intel-specific kernel DRM services --
runtime
ii libdrm-nouveau2:amd64 2.4.74-1
amd64 Userspace interface to nouveau-specific kernel DRM services --
runtime
ii libdrm-radeon1:amd64 2.4.74-1
amd64 Userspace interface to radeon-specific kernel DRM services --
runtime
ii libdrm2:amd64 2.4.74-1
amd64 Userspace interface to kernel DRM services -- runtime
ii libva-drm1:amd64 1.7.3-2
amd64 Video Acceleration (VA) API for Linux -- DRM runtime
# dpkg -l | fgrep -i dri
...
ii i965-va-driver:amd64 1.7.3-1
amd64 VAAPI driver for Intel G45 & HD Graphics family
...
ii libgl1-mesa-dri:amd64 13.0.3-1
amd64 free implementation of the OpenGL API -- DRI modules
...
ii libvdpau-va-gl1:amd64 0.4.2-1
amd64 VDPAU driver with OpenGL/VAAPI backend
ii libxcb-dri2-0:amd64 1.12-1
amd64 X C Binding, dri2 extension
ii libxcb-dri3-0:amd64 1.12-1
amd64 X C Binding, dri3 extension
...
ii va-driver-all:amd64 1.7.3-2
amd64 Video Acceleration (VA) API -- driver metapackage
ii vdpau-va-driver:amd64 0.7.4-6
amd64 VDPAU-based backend for VA API
...
ii xserver-xorg-video-intel 2:2.99.917+git20161206-1
amd64 X.Org X server -- Intel i8xx, i9xx display driver
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170131/8ab5ea3b/attachment.html>
More information about the intel-gfx-bugs
mailing list