Bug 85903 - [DP MST] intel monitor hotplug
Summary: [DP MST] intel monitor hotplug
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
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: 2014-11-05 08:29 UTC by Nicola
Modified: 2017-07-24 22:50 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg with drm.debug=0xe (181.86 KB, text/plain)
2014-11-26 07:25 UTC, Nicola 		no flags Details
View All

Description Nicola 2014-11-05 08:29:26 UTC 
xorg 1.16.1 intel driver 2.99.916, every time i connect disconnect my external display I get this trace:

[ 2866.466461] CPU: 0 PID: 185 Comm: kworker/0:2 Tainted: G        W  O   3.17.2-1-ARCH #1
[ 2866.466463] Hardware name: LENOVO 20BE0065IX/20BE0065IX, BIOS GMET66WW (2.14 ) 07/01/2014
[ 2866.466473] Workqueue: events i915_hotplug_work_func [i915]
[ 2866.466475]  0000000000000000 0000000000dfeb71 ffff880232f93c90 ffffffff815367d0
[ 2866.466478]  ffff880232f93cd8 ffff880232f93cc8 ffffffff8107054d ffff8800ab0f20e0
[ 2866.466480]  0000000000000000 ffff8800aa840000 0000000000000011 0000000000000003
[ 2866.466483] Call Trace:
[ 2866.466488]  [<ffffffff815367d0>] dump_stack+0x4d/0x6f
[ 2866.466492]  [<ffffffff8107054d>] warn_slowpath_common+0x7d/0xa0
[ 2866.466495]  [<ffffffff810705cc>] warn_slowpath_fmt+0x5c/0x80
[ 2866.466505]  [<ffffffffa0389e5b>] ? drm_dp_dpcd_read+0x1b/0x20 [drm_kms_helper]
[ 2866.466517]  [<ffffffffa04a9f12>] edp_panel_vdd_off.part.12+0x62/0x70 [i915]
[ 2866.466529]  [<ffffffffa04aa880>] intel_dp_probe_mst.part.13+0xb0/0xf0 [i915]
[ 2866.466540]  [<ffffffffa04ab559>] intel_dp_detect+0xa9/0x230 [i915]
[ 2866.466552]  [<ffffffffa0463948>] i915_hotplug_work_func+0x1f8/0x310 [i915]
[ 2866.466556]  [<ffffffff81088b85>] process_one_work+0x145/0x400
[ 2866.466559]  [<ffffffff8108914b>] worker_thread+0x6b/0x4a0
[ 2866.466561]  [<ffffffff810890e0>] ? init_pwq.part.22+0x10/0x10
[ 2866.466564]  [<ffffffff8108e06a>] kthread+0xea/0x100
[ 2866.466566]  [<ffffffff8108df80>] ? kthread_create_on_node+0x1b0/0x1b0
[ 2866.466569]  [<ffffffff8153c6fc>] ret_from_fork+0x7c/0xb0
[ 2866.466572]  [<ffffffff8108df80>] ? kthread_create_on_node+0x1b0/0x1b0
[ 2866.466573] ---[ end trace 3a7bc5d023caa45d ]---

the system show no visible issues
Comment 1 Daniel Vetter 2014-11-25 09:26:41 UTC 
Can you please boot with drm.debug=0xe, reproduce the issue and then attach the complete dmesg (i.e. from boot-up to the backtrace)? Also adding Dave because MST.
Comment 2 Daniel Vetter 2014-11-25 09:26:52 UTC 
Oh and: Is this a regression?
Comment 3 Nicola 2014-11-26 07:25:08 UTC 
Created attachment 110036 [details]
dmesg with drm.debug=0xe

I don't known if this is a regression
Comment 4 Nicola 2015-01-22 08:19:34 UTC 
fixed with the latest update

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.