Bug 92972 - Black screen on Intel NUC hardware (i915) possible kernel regression
Summary: Black screen on Intel NUC hardware (i915) possible kernel regression
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Elio
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-16 21:54 UTC by Vivek Dasmohapatra
Modified: 2017-06-30 23:43 UTC (History)
3 users (show)

See Also:
i915 platform: BDW
i915 features: display/DP


Attachments
dmesg on a NUC DN2820FYK with drm.debug=14 (72.48 KB, text/plain)
2016-06-21 13:38 UTC, Aristeu Rozanski
no flags Details
dmesg running drm-intel-nightly (74.50 KB, text/plain)
2016-06-21 15:21 UTC, Aristeu Rozanski
no flags Details

Description Vivek Dasmohapatra 2015-11-16 21:54:43 UTC
Several users on the 01.org linuxgraphics forum have reported a black
screen when booting Inte NUCs, with various approaches solving the
problem, including:

 - switching to a DVI-DBI cable from some other type
 - changing the connected monitor
 - downgrading from a 4.x kernel to a late 3.x series kernel

Since it's not clear if these are all the same bug these reports
are being collected here at Intel's request so they can be investigated.

The main discussion thread:

https://01.org/linuxgraphics/forum/graphics-installer-discussions/nuc5i3ryh-black-screen-debian

Some solutions from that thread:


    Using a Dell monitor connected via a VGA cable 
    to a miniDisplayPort to VGA adapter. After 
    Switching to a Samsung monitor hooked up via DVI and a miniDisplayPort
    to DVI adapter, all my problems went away

    Fresh install and  dnf update which installed 4.1.7-200.fc22.x86_64
    reproduced the problem. 
    With this as the machine's current state 4.0.4-301.fc22.x86_64
    works fine.

    I went through the
    https://wiki.archlinux.org/index.php/Intel_graphics
    and couldnt get it working on debian testing. 
    NB: Probably kernel 4.1 at the time.
    ... well I though of trying stable kernel... added all apt source 
    entries of stable repos and added 3.16 kernel... AND IT WORKS.
Comment 1 Jani Nikula 2015-11-17 09:59:32 UTC
Please add drm.debug=14 module parameter and attach dmesg all the way from boot to the problem.

Please try v4.3 or later kernel.

It's likely this has to do with DP->VGA dongles, based on the reports.
Comment 2 cprigent 2015-12-01 17:10:54 UTC
Elio,
Could you have a try and provide the log.
Comment 3 Elio 2015-12-09 19:42:49 UTC
I'm trying to reproduce the issue stressing the system, no positive results so far, i will try to stress the system a few hours and see what happen.
Comment 4 Elio 2015-12-10 15:38:42 UTC
I'm not able to reproduce the problem so far, my configuration:

Ubuntu 15.10 with 3.10.26 Kernel

Stressing the system with stress for more than 8 hours:

"stress -c 10 -m1 --vm 2 --vm-bytes 8192M"

All cpus are over 100% 
Memory (7.7 GiB) 100%  Swap(7.9 GiB) 50%

Using a Dell Monitor thourgh VGA with a Mini Display - Vga Dongle.

Brand:  Startech.

I'm just wondering if we can get the dongle brand since it seems to be difference on the setup
Comment 5 annonm 2016-01-15 18:25:24 UTC
I have a NUC5i7, not an i3, and do not suffer from the problem. My hardware does identify itself as i915. Let me know if I can be any use in testing.
Comment 6 ravi mannan 2016-01-18 02:11:42 UTC
I am having the same problem. Here's some info on my configuration.
Let me know if you need more info. The 2nd monitor connected via hdmi is the one that blacks out, not the laptop screen itself.
No, it's not a problem with my hdmi cable or monitor, those both work on with another computer.

uname -a
Linux ravimannan-P34V4 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
ravimannan@ravimannan-P34V4 /data $ 


ravimannan@ravimannan-P34V4 /data $ sudo inxi -AG -b
System:    Host: ravimannan-P34V4 Kernel: 3.19.0-32-generic x86_64 (64 bit) Desktop: Cinnamon 2.8.6
           Distro: Linux Mint 17.3 Rosa
Machine:   Mobo: GIGABYTE model: P34V4 Bios: American Megatrends v: FB04 date: 07/22/2015
CPU:       Quad core Intel Core i7-5700HQ (-HT-MCP-) speed/max: 2700/3500 MHz
Graphics:  Card: Intel Broadwell-U Integrated Graphics
           Display Server: X.org 1.17.1 drivers: intel (unloaded: fbdev,vesa)
           tty size: 122x61 Advanced Data: N/A for root
Audio:     Card-1 Intel Broadwell-U Audio Controller driver: snd_hda_intel Sound: ALSA v: k3.19.0-32-generic
           Card-2 Intel Device 8ca0 driver: snd_hda_intel
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           Card-2: Intel Wireless 7260 driver: iwlwifi
Drives:    HDD Total Size: 1128.2GB (0.7% used)
Info:      Processes: 234 Uptime: 4:27 Memory: 1777.3/7895.9MB Client: Shell (sudo) inxi: 2.2.28 


ravimannan@ravimannan-P34V4 /data $ xrandr
Screen 0: minimum 8 x 8, current 5360 x 1440, maximum 32767 x 32767
eDP1 connected 1920x1080+0+16 (normal left inverted right x axis y axis) 309mm x 175mm
   1920x1080      60.0*+   59.9  
   1680x1050      60.0     59.9  
   1600x1024      60.2  
   1400x1050      60.0  
   1280x1024      60.0  
   1440x900       59.9  
   1280x960       60.0  
   1360x768       59.8     60.0  
   1152x864       60.0  
   1024x768       60.0  
   800x600        60.3     56.2  
   640x480        59.9  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected primary 3440x1440+1920+0 (normal left inverted right x axis y axis) 800mm x 335mm
   3440x1440      50.0*+   30.0  
   2560x1080      60.0  
   1920x1080      60.0     60.0     59.9  
   1680x1050      59.9  
   1600x900       60.0  
   1280x1024      60.0  
   1280x800       59.9  
   1152x864       60.0  
   1280x720       60.0     59.9  
   1024x768       60.0  
   800x600        60.3  
   720x480        60.0     59.9  
   640x480        60.0     59.9  
HDMI2 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Comment 7 ravi mannan 2016-01-25 23:01:06 UTC
I have a dual boots system. I've been using Windows 10 and I am not seeing this problem. It is not the cable , hdmi port or monitor.
Comment 8 ravi mannan 2016-01-26 16:43:21 UTC
It doesn't seem to be happening at a lower resolution of    2560x1080:

HDMI1 connected 2560x1080+1920+0 800mm x 335mm
   3440x1440      50.0 +   30.0  
   2560x1080      60.0*
Comment 9 Aristeu Rozanski 2016-06-21 13:38:21 UTC
Created attachment 124638 [details]
dmesg on a NUC DN2820FYK with drm.debug=14
Comment 10 Aristeu Rozanski 2016-06-21 13:41:26 UTC
Seeing the same issue with a 4.6+ kernel, NUC DN2820FYK. I'm using a HDMI/DVI dongle.
Comment 11 Jani Nikula 2016-06-21 14:42:43 UTC
Please try drm-intel-nightly branch of [1] and report back.

[1] http://cgit.freedesktop.org/drm-intel
Comment 12 Aristeu Rozanski 2016-06-21 15:21:51 UTC
Created attachment 124641 [details]
dmesg running drm-intel-nightly

HEAD: 9d436e8b52d869ff27f49185e865f8e7d36fa4d7
Comment 13 Jani Nikula 2016-06-29 10:05:34 UTC
(In reply to Aristeu Rozanski from comment #12)
> Created attachment 124641 [details]
> dmesg running drm-intel-nightly
> 
> HEAD: 9d436e8b52d869ff27f49185e865f8e7d36fa4d7

So is that working or not?
Comment 14 Aristeu Rozanski 2016-06-29 12:56:15 UTC
No, same behavior.
Comment 15 Elio 2016-08-29 20:23:49 UTC
(In reply to Aristeu Rozanski from comment #14)
> No, same behavior.

Hello Aristeu,

I was trying to replicate the issue in my nuc here, but i wanst possible, could you share all the hardware configuration that you are using? I'm loosing something important.

Currently i was able to setup this platform with 3 monitors, 1 of them 4k. 

It should be great if you can post all your hardware in order to dismiss cables/monitors. etc.
Comment 16 Elio 2016-08-29 20:24:48 UTC
I just forgot to say that i was trying to reproduce the issue with Kernel 4.8.0


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.