[Bug 98282] [skl][bisected] GPU Hangs on drm-intel-nightly
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Nov 2 23:38:34 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=98282
--- Comment #19 from Artjom Simon <artjom.simon at gmail.com> ---
I'm getting a similar WARN_ON_ONCE with current nightly with these patches
seemingly already applied (GNU patch complains "Reversed (or previously
applied) patch detected!" on both).
What can we do to debug this further?
[ 2.140178] ------------[ cut here ]------------
[ 2.140261] WARNING: CPU: 3 PID: 46 at drivers/gpu/drm/i915/intel_dp.c:4022
intel_dp_check_link_status+0x1d7/0x200 [i915]
[ 2.140263] WARN_ON_ONCE(!intel_dp->lane_count)
[ 2.140272] Modules linked in: i915 video button intel_gtt i2c_algo_bit
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm
[ 2.140276] CPU: 3 PID: 46 Comm: kworker/3:1 Not tainted
4.9.0-1-drm-intel-nightly #1
[ 2.140278] Hardware name: Dell Inc. XPS 13 9350/07TYC2, BIOS 1.4.4
06/14/2016
[ 2.140286] Workqueue: events output_poll_execute [drm_kms_helper]
[ 2.140292] ffffc90000e13bc8 ffffffff812f8de0 ffffc90000e13c18
0000000000000000
[ 2.140295] ffffc90000e13c08 ffffffff8107cddb 00000fb600e13c40
ffff8802760270f0
[ 2.140299] 0000000000000001 ffff880273c58000 ffff880273c58258
ffff880276027000
[ 2.140300] Call Trace:
[ 2.140307] [<ffffffff812f8de0>] dump_stack+0x63/0x83
[ 2.140312] [<ffffffff8107cddb>] __warn+0xcb/0xf0
[ 2.140315] [<ffffffff8107ce5f>] warn_slowpath_fmt+0x5f/0x80
[ 2.140322] [<ffffffffa007d467>] ? drm_dp_dpcd_read+0x57/0x70
[drm_kms_helper]
[ 2.140386] [<ffffffffa0172e67>] intel_dp_check_link_status+0x1d7/0x200
[i915]
[ 2.140445] [<ffffffffa01790b7>] intel_dp_detect+0x697/0xa40 [i915]
[ 2.140452] [<ffffffffa007e15f>]
drm_helper_probe_single_connector_modes+0x3ff/0x4f0 [drm_kms_helper]
[ 2.140459] [<ffffffffa008d26b>] drm_fb_helper_hotplug_event+0x10b/0x150
[drm_kms_helper]
[ 2.140516] [<ffffffffa0169a14>] intel_fbdev_output_poll_changed+0x24/0x30
[i915]
[ 2.140522] [<ffffffffa007da27>] drm_kms_helper_hotplug_event+0x27/0x30
[drm_kms_helper]
[ 2.140528] [<ffffffffa007dc28>] output_poll_execute+0x198/0x1e0
[drm_kms_helper]
[ 2.140533] [<ffffffff81096b35>] process_one_work+0x1e5/0x470
[ 2.140537] [<ffffffff81096e08>] worker_thread+0x48/0x4e0
[ 2.140541] [<ffffffff81096dc0>] ? process_one_work+0x470/0x470
[ 2.140544] [<ffffffff81096dc0>] ? process_one_work+0x470/0x470
[ 2.140547] [<ffffffff8109c999>] kthread+0xd9/0xf0
[ 2.140551] [<ffffffff8102d752>] ? __switch_to+0x2d2/0x630
[ 2.140553] [<ffffffff8109c8c0>] ? kthread_park+0x60/0x60
[ 2.140559] [<ffffffff815fbdd5>] ret_from_fork+0x25/0x30
[ 2.140562] ---[ end trace 4fe5657f076aec76 ]---
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161102/3fdca6fc/attachment.html>
More information about the intel-gfx-bugs
mailing list