| Summary: | [IVB bisected] [drm:intel_dp_aux_ch] *ERROR* dp aux hw did not signal timeout (has irq: 1)! | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Chris Bainbridge <chris.bainbridge> | ||||
| Component: | DRM/Intel | Assignee: | Manasi <manasi.d.navare> | ||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Severity: | critical | ||||||
| Priority: | high | CC: | intel-gfx-bugs | ||||
| Version: | DRI git | Keywords: | bisected, regression | ||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | IVB | i915 features: | display/DP | ||||
| Attachments: |
|
||||||
|
Description
Chris Bainbridge
2016-06-07 19:31:42 UTC
Which kernel are you running? Please try current drm-intel-nightly branch of http://cgit.freedesktop.org/drm-intel Bug appears in Linus tree from 2d65a9f48fcd where the two commits identified above were merged together up to latest v4.7-rc5. Bug is still present in drm-intel-nightly v4.7-rc5-832-ga90c9899ce2f, after 30 reboots: [ 1.392565] [drm:intel_dp_aux_ch] *ERROR* dp aux hw did not signal timeout (has irq: 1)! [ 1.415537] [drm:intel_dp_aux_ch] *ERROR* dp aux hw did not signal timeout (has irq: 1)! [ 1.438534] [drm:intel_dp_aux_ch] *ERROR* dp aux hw did not signal timeout (has irq: 1)! Chris - I'm really sorry about this long delay until getting back to you. There has been quite a few changes/fixes introduced, so please retest (again) with the latest kernels (preferable from drm-tip), and mark status as REOPENED if problem still persist. Attach logs etc. as instructed in https://01.org/linuxgraphics/documentation/how-report-bugs. Chris, did you get a chance to run against the latest drm-tip since there have been lot of changes since 4.7. Just want to understand if this is still valid and if you still see it please send us the dmesg logs with DRM.DEBUG set to 0xe and we can help triage/fix this. Manasi Hello
I just tried to reproduce the problem with following configuration:
HSW NUC, using mini-DP, external monitor (asus) 1920x1080.
HSW NUC, using mini-DP with MST DP-DP, external monitor (asus) 1920x1080.
HSW NUC, using mini-DP, external monitor (acer) 3840 x 2160
HSW NUC, using mini-DP with MST DP-DP, external monitor (acer) 3840 x 2160
Attaching my configuration used to test
======================================
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
I did not have any issue.
This configuration works for me.
|
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.