Bug 98567 - [SKL]Black screen : no signal from computer
Summary: [SKL]Black screen : no signal from computer
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-03 11:28 UTC by martin.souchal
Modified: 2017-03-08 10:02 UTC (History)
1 user (show)

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


Attachments

Description martin.souchal 2016-11-03 11:28:01 UTC
I'm using an external monitor plugged with mDP to my HP EliteBook Folio 1040 G3 laptop.

There is no image at all, the screen is black from boot. 

uname :
Linux 4.8.6-1-ARCH #1 SMP PREEMPT Mon Oct 31 18:51:30 CET 2016 x86_64 GNU/Linux

xrandr output :
Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767
eDP1 connected primary 1920x1080+1044+0 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     60.01*+  40.00  
   1400x1050     59.98  
   1600x900      60.00  
   1280x1024     60.02  
   1280x960      60.00  
   1368x768      60.00  
   1280x720      60.00  
   1024x768      60.00  
   1024x576      60.00  
   960x540       60.00  
   800x600       60.32    56.25  
   864x486       60.00  
   640x480       59.94  
   720x405       60.00  
   640x360       60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP2-1 connected 3840x2160+0+1080 (normal left inverted right x axis y axis) 530mm x 300mm
   3840x2160     60.00*+  29.98  
   2560x1440     59.95  
   2048x1280     59.99  
   1920x1200     59.88  
   1920x1080     60.00    60.00    50.00    59.94    24.00    23.98  
   1600x1200     60.00  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    60.00    59.94  
   720x400       70.08  
DP2-2 disconnected (normal left inverted right x axis y axis)
DP2-3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

dmesg error message :
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[   33.096244] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, aborting
[   33.681622] fuse init (API version 7.25)
[  149.138287] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[  149.756668] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[  150.374918] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[  150.993109] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[  151.613104] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[  152.231252] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[  152.849672] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up
[  152.849885] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, aborting
[  152.858138] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns
[  165.458248] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun


lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)



Thanks
Comment 1 Jani Saarinen 2016-12-09 10:05:04 UTC
Is this still valid?
Comment 2 martin.souchal 2016-12-09 10:43:52 UTC
It's still valid with Linux 4.9.0-1-drm-intel-nightly #1 SMP PREEMPT Mon Dec 5 12:56:56 CET 2016 x86_64 GNU/Linux

Error in dmesg :

[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

and before :

[    3.467590] ------------[ cut here ]------------
[    3.467634] WARNING: CPU: 2 PID: 46 at drivers/gpu/drm/i915/intel_dp.c:4023 intel_dp_check_link_status+0x1d7/0x200 [i915]
[    3.467636] WARN_ON_ONCE(!intel_dp->lane_count)
[    3.467663] Modules linked in: snd_compress snd_pcm_dmaengine ac97_bus uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media iTCO_wdt mei_wdt(+) iTCO_vendor_support i2c_designware_platform(+) i2c_designware_core hp_wmi arc4 tpm_infineon intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_cstate intel_rapl_perf btusb btrtl pcspkr evdev input_leds psmouse mac_hid iwlmvm snd_hda_intel mac80211 snd_hda_codec e1000e led_class i915 snd_hda_core ptp snd_hwdep pps_core snd_pcm drm_kms_helper snd_timer snd soundcore iwlwifi i2c_i801 i2c_smbus cfg80211 drm intel_gtt syscopyarea shpchp sysfillrect mei_me sysimgblt fb_sys_fops
[    3.467684]  i2c_algo_bit idma64 intel_pch_thermal mei intel_lpss_pci thermal wmi battery i2c_hid hid hci_uart btbcm btqca btintel bluetooth rfkill pinctrl_sunrisepoint pinctrl_intel intel_lpss_acpi intel_lpss video fjes hp_wireless intel_hid acpi_pad ac sparse_keymap tpm_tis tpm_tis_core button tpm sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 mbcache dm_mod sd_mod serio_raw atkbd libps2 crc32c_intel ahci libahci libata xhci_pci xhci_hcd scsi_mod usbcore usb_common i8042 serio
[    3.467687] CPU: 2 PID: 46 Comm: kworker/2:1 Tainted: G     U          4.9.0-1-drm-intel-nightly #1
[    3.467688] Hardware name: HP HP EliteBook Folio 1040 G3/80FA, BIOS N83 Ver. 01.08 09/02/2016
[    3.467693] Workqueue: events output_poll_execute [drm_kms_helper]
[    3.467696]  ffffc90000e17b30 ffffffff812f9a70 ffffc90000e17b80 0000000000000000
[    3.467698]  ffffc90000e17b70 ffffffff8107d4db 00000fb700e17ba8 ffff880224d5d0f0
[    3.467700]  0000000000000001 ffff880226338000 ffff880226338258 ffff880224d5d000
[    3.467701] Call Trace:
[    3.467705]  [<ffffffff812f9a70>] dump_stack+0x63/0x83
[    3.467708]  [<ffffffff8107d4db>] __warn+0xcb/0xf0
[    3.467710]  [<ffffffff8107d55f>] warn_slowpath_fmt+0x5f/0x80
[    3.467714]  [<ffffffffa0589467>] ? drm_dp_dpcd_read+0x57/0x70 [drm_kms_helper]
[    3.467751]  [<ffffffffa066f187>] intel_dp_check_link_status+0x1d7/0x200 [i915]
[    3.467783]  [<ffffffffa0675489>] intel_dp_detect+0x6a9/0xa50 [i915]
[    3.467787]  [<ffffffffa058a020>] drm_helper_probe_single_connector_modes+0x2a0/0x500 [drm_kms_helper]
[    3.467791]  [<ffffffffa059837b>] drm_setup_crtcs+0x7b/0x9b0 [drm_kms_helper]
[    3.467794]  [<ffffffff812fd2ec>] ? kobject_uevent_env+0x14c/0x4f0
[    3.467797]  [<ffffffffa05991c2>] drm_fb_helper_hotplug_event+0xd2/0xf0 [drm_kms_helper]
[    3.467831]  [<ffffffffa0665bc4>] intel_fbdev_output_poll_changed+0x24/0x30 [i915]
[    3.467835]  [<ffffffffa0589a27>] drm_kms_helper_hotplug_event+0x27/0x30 [drm_kms_helper]
[    3.467838]  [<ffffffffa0589c4c>] output_poll_execute+0x1bc/0x200 [drm_kms_helper]
[    3.467841]  [<ffffffff81097245>] process_one_work+0x1e5/0x470
[    3.467843]  [<ffffffff81097518>] worker_thread+0x48/0x4e0
[    3.467845]  [<ffffffff810974d0>] ? process_one_work+0x470/0x470
[    3.467847]  [<ffffffff810974d0>] ? process_one_work+0x470/0x470
[    3.467848]  [<ffffffff8109d0a9>] kthread+0xd9/0xf0
[    3.467851]  [<ffffffff8102d752>] ? __switch_to+0x2d2/0x630
[    3.467853]  [<ffffffff8109cfd0>] ? kthread_park+0x60/0x60
[    3.467855]  [<ffffffff815fd8d5>] ret_from_fork+0x25/0x30
[    3.467856] ---[ end trace 692125c45b30cbcb ]---
Comment 3 Jani Saarinen 2017-03-08 07:40:39 UTC
With latest changes on atomic/watermark can you test with drm-tip if issue is seen still?
Comment 4 martin.souchal 2017-03-08 08:48:47 UTC
No it's good, problem resolved.
Thanks


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.