Bug 101296 - [DP][SKL] i915 System Hangup with Display port connect to Display
Summary: [DP][SKL] i915 System Hangup with Display port connect to Display
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium blocker
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-04 16:02 UTC by wanglei
Modified: 2017-06-29 20:12 UTC (History)
1 user (show)

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


Attachments
ERROR INFO (3.53 MB, image/jpeg)
2017-06-04 16:02 UTC, wanglei
no flags Details

Description wanglei 2017-06-04 16:02:36 UTC
Created attachment 131698 [details]
ERROR INFO

System Info :
  
   laptop: Dell E5270
   cpu: Intel(R) Core(TM) i5-6200U
   Graphic: Intel HD520
   Kernel: 4.4.35-1
   libdrm: 2.4.75
Error info:
   When connect a Display to the laptop VGA Display port,system hangup and print
[drm: intel_dp_link_trainning_clock_recovery [i915] *ERROR* too many full retries.give up 
........
........
........
Comment 1 Jari Tahvanainen 2017-06-05 07:32:20 UTC
Hello Wanglei, is system hangup occasional or 100% reproducible?
Your kernel version is quite old. Please try to reproduce the failure with the latest kernel (canonical/kernel.org longterm 4.4.70 or preferable with drm-tip or stable 4.11.3) and provide the logs from that as instructed in https://01.org/linuxgraphics/documentation/how-report-bugs. 
It might also help if you can attach i915_display_info file from /sys/kernel/debug/dri/0 (if you can generate image from drm-tip with debugfs enabled).
Comment 2 Armando Antonio 2017-06-29 20:12:37 UTC
I tried to reproduce this bug but I could not reproduce with the following configuration:

======================================
        Graphic stack
======================================

======================================
             Software
======================================
kernel version              : 4.12.0-rc3-drm-tip-ww22-commit-187376e+
architecture                : x86_64
os version                  : Ubuntu 17.04
os codename                 : zesty
kernel driver               : i915
bios revision               : 4.6
bios release date           : 03/02/2017

======================================
        Graphic drivers
======================================
mesa                        : 17.0.3
modesetting                 : modesetting_drv.so
xorg-xserver                : 1.19.3
libdrm                      : 2.4.81
cairo                       : 1.14.8
xserver                     : X.Org X Server 1.19.99.1
intel-gpu-tools (tag)       : intel-gpu-tools-1.18-211-g00ce341b
intel-gpu-tools (commit)    : 00ce341b

======================================
             Hardware
======================================
platform                   : HSW-Nuc
motherboard id             : D54250WYK
form factor                : Desktop
cpu family                 : Core i5
cpu family id              : 6
cpu information            : Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz
gpu card                   : Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
memory ram                 : 3.79 GB
max memory ram             : 16 GB
display resolution         : 1600x900
cpu thread                 : 4
cpu core                   : 2
cpu model                  : 69
cpu stepping               : 1
socket                     : Socket LGA1150
signature                  : Type 0, Family 6, Model 69, Stepping 1
hard drive                 : 223GiB (240GB)
current cd clock frequency : 450000 kHz
maximum cd clock frequency : 450000 kHz
displays connected         : DP-1

======================================
             Firmware
======================================

======================================
             kernel parameters
======================================
quiet splash fastboot drm.debug=0xe


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.