Bug 89552 - [SKL] Attempting AUX transfer with eDP off from drm_mode_getcrtc()
Summary: [SKL] Attempting AUX transfer with eDP off from drm_mode_getcrtc()
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-12 07:29 UTC by Ding Heng
Modified: 2017-03-08 10:03 UTC (History)
2 users (show)

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


Attachments
dmesg (1.74 MB, text/plain)
2015-03-12 07:29 UTC, Ding Heng
no flags Details
dmesg (123.70 KB, text/plain)
2015-08-24 13:29 UTC, Rami
no flags Details

Description Ding Heng 2015-03-12 07:29:18 UTC
Created attachment 114241 [details]
dmesg

System Environment:
--------------------------
Regression: not sure

no-working platforms: SKL

==kernel==
--------------------------
nightly branch: c09a3b7f343bc87a132ef107cb263e57f8246b88(2015-03-10)

==Bug detailed description==
-----------------------------
root@x-skly03:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg -r | egrep "<[1-4]>" |grep drm
<4>[  141.410057] WARNING: CPU: 0 PID: 5172 at drivers/gpu/drm/i915/intel_dp.c:658 intel_dp_aux_ch+0xaa/0x57f [i915]()
<4>[  141.410062] Modules linked in: dm_mod snd_hda_codec_realtek snd_hda_codec_generic ppdev snd_hda_intel snd_hda_controller i2c_i801 pcspkr snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore wmi battery parport_pc parport ac acpi_cpufreq i915 button video drm_kms_helper drm
<4>[  141.410241]  [<ffffffffa00515db>] ? drm_dp_dpcd_access+0x5b/0xed [drm_kms_helper]
<4>[  141.410250]  [<ffffffffa0051680>] ? drm_dp_dpcd_read+0x13/0x17 [drm_kms_helper]
<4>[  141.410336]  [<ffffffffa0051e88>] ? drm_helper_probe_single_connector_modes_merge_bits+0xc4/0x395 [drm_kms_helper]
<4>[  141.410354]  [<ffffffffa000ef5d>] ? drm_mode_getconnector+0xda/0x2aa [drm]
<4>[  141.410369]  [<ffffffffa00047d4>] ? drm_ioctl+0x344/0x3b3 [drm]
<4>[  141.410391]  [<ffffffffa000ee83>] ? drm_mode_getcrtc+0xfe/0xfe [drm]
<4>[  141.410405]  [<ffffffffa0003b60>] ? drm_gem_vm_close+0x2a/0x4b [drm]
root@x-skly03:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# dmesg -r | egrep "<[1-4]>" |grep call
<4>[  141.410424]  [<ffffffff81799972>] ? system_call_fastpath+0x12/0x17

==Reproduce steps==
---------------------------- 
1. ./kms_universal_plane
Comment 1 Damien Lespiau 2015-03-12 15:41:25 UTC
Just for record, I've seen several times that people extrace traces grping on the log level, that's not giving the whole picture. It'd be better to have the whole trace:

[  141.410019] ------------[ cut here ]------------
[  141.410057] WARNING: CPU: 0 PID: 5172 at drivers/gpu/drm/i915/intel_dp.c:658 intel_dp_aux_ch+0xaa/0x57f [i915]()
[  141.410059] eDP powered off while attempting aux channel communication.
[  141.410062] Modules linked in: dm_mod snd_hda_codec_realtek snd_hda_codec_generic ppdev snd_hda_intel snd_hda_controller i2c_i801 pcspkr snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore wmi battery parport_pc parport ac acpi_cpufreq i915 button video drm_kms_helper drm
[  141.410092] CPU: 0 PID: 5172 Comm: kms_universal_p Not tainted 4.0.0-rc3_kcloud_62f93b_20150310+ #2
[  141.410096] Hardware name: Intel Corporation Skylake Client platform/Skylake Y LPDDR3 RVP3, BIOS SKLSE2R1.86C.B068.R00.1501090908 01/09/2015
[  141.410099]  0000000000000000 0000000000000009 ffffffff81794128 ffff88009a797a68
[  141.410105]  ffffffff8103bd5a ffff880004c424f8 ffffffffa00ea255 0000000000000000
[  141.410110]  ffff880004c420e0 ffff880143f70000 ffff880143f70000 ffff880004c424a8
[  141.410116] Call Trace:
[  141.410127]  [<ffffffff81794128>] ? dump_stack+0x40/0x50
[  141.410135]  [<ffffffff8103bd5a>] ? warn_slowpath_common+0x98/0xb0
[  141.410161]  [<ffffffffa00ea255>] ? intel_dp_aux_ch+0xaa/0x57f [i915]
[  141.410168]  [<ffffffff8103bdb7>] ? warn_slowpath_fmt+0x45/0x4a
[  141.410193]  [<ffffffffa00ea255>] ? intel_dp_aux_ch+0xaa/0x57f [i915]
[  141.410200]  [<ffffffff81064f70>] ? wait_woken+0x7c/0x7c
[  141.410225]  [<ffffffffa00ea828>] ? intel_dp_aux_transfer+0xfe/0x127 [i915]
[  141.410232]  [<ffffffff81798243>] ? mutex_lock+0x9/0x25
[  141.410241]  [<ffffffffa00515db>] ? drm_dp_dpcd_access+0x5b/0xed [drm_kms_helper]
[  141.410250]  [<ffffffffa0051680>] ? drm_dp_dpcd_read+0x13/0x17 [drm_kms_helper]
[  141.410273]  [<ffffffffa00e64fb>] ? intel_dp_dpcd_read_wake+0x3a/0x64 [i915]
[  141.410279]  [<ffffffff81798243>] ? mutex_lock+0x9/0x25
[  141.410302]  [<ffffffffa00e9523>] ? intel_dp_probe_oui+0x2a/0xaf [i915]
[  141.410326]  [<ffffffffa00e99ac>] ? intel_dp_detect+0x111/0x169 [i915]
[  141.410336]  [<ffffffffa0051e88>] ? drm_helper_probe_single_connector_modes_merge_bits+0xc4/0x395 [drm_kms_helper]
[  141.410354]  [<ffffffffa000ef5d>] ? drm_mode_getconnector+0xda/0x2aa [drm]
[  141.410369]  [<ffffffffa00047d4>] ? drm_ioctl+0x344/0x3b3 [drm]
[  141.410376]  [<ffffffff810eed43>] ? tlb_finish_mmu+0x1e/0x2f
[  141.410391]  [<ffffffffa000ee83>] ? drm_mode_getcrtc+0xfe/0xfe [drm]
[  141.410405]  [<ffffffffa0003b60>] ? drm_gem_vm_close+0x2a/0x4b [drm]
[  141.410413]  [<ffffffff8111fb0e>] ? do_vfs_ioctl+0x360/0x424
[  141.410420]  [<ffffffff8111fc1b>] ? SyS_ioctl+0x49/0x7a
[  141.410424]  [<ffffffff81799972>] ? system_call_fastpath+0x12/0x17
[  141.410428] ---[ end trace 4c6bc5d7d0a9c4c7 ]---
Comment 2 Chris Wilson 2015-03-12 20:51:32 UTC
Especially something that can be easily captured and reported by igt...
Comment 3 cprigent 2015-08-03 22:42:55 UTC
Bug scrub: assigned to Rami
Rami, could you check if still reproduced.
Comment 4 Rami 2015-08-24 13:29:17 UTC
Created attachment 117894 [details]
dmesg

Tested with skl. There are dmesg errors in the end of test.

System Environment:
==================
SKY LAKE-Y4
Hardware
Platform: SKY LAKE Y A0 
CPU : Intel(R) Core(TM) m5-6Y57 CPU @ 1.10GHz (family: 6, model: 78  stepping: 3)
MCP : SKL-Y  D0 2+2 (ou ULX-D1)
QDF : QJA4 
CPU : SKL D0
Chipset PCH: Sunrise Point LP C1       
CRB : SKY LAKE Y LPDDR3 RVP3 CRB FAB2
Reworks : All Mandatories 

Software: 
=========
Linux distribution: Ubuntu 14.04 LTS 64 bits 
Kernel:  
BIOS : SKLSE2R1.R00.X093.B02.1507222151
ME FW : 11.0.0.1163
Ksc (EC FW): 1.16
Kernel: drm-intel-nightly 30263ef782e0548c114fb6f2771b58b27c56ba0d 4.2.0-rc7 from git://anongit.freedesktop.org/drm-intel
Mesa: mesa-10.6.3 ddc976368fef367e464472ebcc2ac4fd89eb9fd8 from http://cgit.freedesktop.org/mesa/mesa/ 
Xf86_video_intel: 2.99.917 baec802b21387d04aebb10ac29e719a1800c5aa0 from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ 
Libdrm: libdrm-2.4.62 ba4b5ac010ab85406ec52e3906e13d58cd9aa782 from http://cgit.freedesktop.org/mesa/drm/ 
Cairo: 1.14.2 93422b3cb5e0ef8104b8194c8873124ce2f5ea2d from http://cgit.freedesktop.org/cairo 
libva: libva-1.6.0 a8008998bc0d4a76ae6927607c048e52ba50fd0e from http://cgit.freedesktop.org/libva/ 
intel-driver: 1.6.0 32268c46d538667d437dc9266aa4c183e51c1286 from http://cgit.freedesktop.org/vaapi/intel-driver 
Xserver: xorg-server-1.17.2 2123f7682d522619f101b05fb75efa75dabbe371 from http://cgit.freedesktop.org/xorg/xserver

Actual Result:
==============
IGT-Version: 1.11-g0e25e5d (x86_64) (Linux: 4.2.0-rc7-drm-intel-nightly-ww34+ x86_64)
Testing connector eDP-1 using pipe A
Subtest universal-plane-pipe-A-functional: SUCCESS (17.490s)
Subtest universal-plane-pipe-A-sanity: SUCCESS (7.996s)
Subtest disable-primary-vs-flip-pipe-A: SUCCESS (4.983s)
Subtest cursor-fb-leak-pipe-A: SUCCESS (5.799s)
Testing connector eDP-1 using pipe B
Subtest universal-plane-pipe-B-functional: SUCCESS (18.718s)
Subtest universal-plane-pipe-B-sanity: SUCCESS (6.256s)
Subtest disable-primary-vs-flip-pipe-B: SUCCESS (2.872s)
Subtest cursor-fb-leak-pipe-B: SUCCESS (0.689s)
Testing connector eDP-1 using pipe C
Subtest universal-plane-pipe-C-functional: SUCCESS (18.805s)
Subtest universal-plane-pipe-C-sanity: SUCCESS (6.178s)
Subtest disable-primary-vs-flip-pipe-C: SUCCESS (2.872s)
Subtest cursor-fb-leak-pipe-C: SUCCESS (0.689s)
[  144.645374] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)!
[  144.656354] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)!
[  144.667345] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)!
[  144.678341] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)!
[  144.689337] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)!
[  144.689384] [drm:intel_dp_aux_ch [i915]] *ERROR* dp_aux_ch not done status 0xad40001f
[  145.841932] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
[  146.033857] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to start channel equalization
Comment 5 Jari Tahvanainen 2017-03-08 08:43:01 UTC
Marking this resolved+fixed based on the WW08 results on Skylake-Nuc.
Comment 4 should have done this already with new bug filed for "failed to enable link training". Unfortunately after so long time it's really hard to dig out the commit that fixed this, so that info is not included here as it should.

igt@kms_universal_plane@cursor-fb-leak-pipe-a		
Pass
igt@kms_universal_plane@cursor-fb-leak-pipe-b		
Pass
igt@kms_universal_plane@cursor-fb-leak-pipe-c		
Pass
igt@kms_universal_plane@disable-primary-vs-flip-pipe-a		
Pass
igt@kms_universal_plane@disable-primary-vs-flip-pipe-b		
Pass
igt@kms_universal_plane@disable-primary-vs-flip-pipe-c		
Pass
igt@kms_universal_plane@universal-plane-gen9-features-pipe-a		
Pass
igt@kms_universal_plane@universal-plane-gen9-features-pipe-b		
Pass
igt@kms_universal_plane@universal-plane-gen9-features-pipe-c		
Pass
igt@kms_universal_plane@universal-plane-pipe-a-functional		
Pass
igt@kms_universal_plane@universal-plane-pipe-a-sanity		
Pass
igt@kms_universal_plane@universal-plane-pipe-b-functional		
Pass
igt@kms_universal_plane@universal-plane-pipe-b-sanity		
Pass
igt@kms_universal_plane@universal-plane-pipe-c-functional		
Pass
igt@kms_universal_plane@universal-plane-pipe-c-sanity		
Pass


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.