[Bug 90059] New: [BYT bisected]Start up the machine with HDMI screen causes WARNING: CPU: 0 PID: 1006 at drivers/gpu/drm/i915/intel_display.c:11997 check_crtc_state+0xb67/0xbd1 [i915]()
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Apr 16 19:07:11 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90059
Bug ID: 90059
Summary: [BYT bisected]Start up the machine with HDMI screen
causes WARNING: CPU: 0 PID: 1006 at
drivers/gpu/drm/i915/intel_display.c:11997
check_crtc_state+0xb67/0xbd1 [i915]()
Product: DRI
Version: unspecified
Hardware: All
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: yex.tian at intel.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 115139
--> https://bugs.freedesktop.org/attachment.cgi?id=115139&action=edit
dmesg info
==System Environment==
---------------------------------------------------
Regression: Yes
Non-working platforms: BYT
==Kernel==
--------------------------------------------------
commit d600654ab94b325f253e267422dcf60302120ea0
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date: Thu Apr 16 17:54:10 2015 +0200
drm-intel-nightly: 2015y-04m-16d-15h-53m-28s UTC integration manifest
==Bug detailed description==
--------------------------------------------------
Start the machine with HDMI screen causes WARNING: CPU: 0 PID: 1006 at
drivers/gpu/drm/i915/intel_display.c:11997 check_crtc_state+0xb67/0xbd1
[i915]() on BYT.
It does not exists with eDP screen.
By bisected, shows the first bad commit is 535afa2.
commit 535afa2e9e3c1867460d6981d879b04d8b2b9ab3
Author: Jesse Barnes <jbarnes at virtuousgeek.org>
AuthorDate: Wed Apr 15 16:52:29 2015 -0700
Commit: Daniel Vetter <daniel.vetter at ffwll.ch>
CommitDate: Thu Apr 16 11:20:30 2015 +0200
drm/i915/vlv: check port in infoframe_enabled v2
Same as IBX and G4x, they all share the same genetic material.
v2: we all need a bit more port in our lives
==output dmesg info==
-----------------------------------------------------------------------
[ 2.195955] ------------[ cut here ]------------
[ 2.196008] WARNING: CPU: 0 PID: 1006 at
drivers/gpu/drm/i915/intel_display.c:11997 check_crtc_state+0xb67/0xbd1
[i915]()
[ 2.196009] pipe state doesn't match!
[ 2.196014] Modules linked in: i915 button video drm_kms_helper drm
[ 2.196018] CPU: 0 PID: 1006 Comm: kworker/u8:3 Not tainted
4.0.0_drm-intel-nightly_d60065_20150417+ #234
[ 2.196025] Workqueue: events_unbound async_run_entry_fn
[ 2.196029] 0000000000000000 0000000000000009 ffffffff81795847
ffff88007994b598
[ 2.196031] ffffffff8103bd5a ffff88007994b590 ffffffffa00c96f0
ffff880175be0000
[ 2.196034] ffff880079a5b000 ffff880175a0c000 ffff88007994b620
ffff8801759ef800
[ 2.196035] Call Trace:
[ 2.196042] [<ffffffff81795847>] ? dump_stack+0x40/0x50
[ 2.196046] [<ffffffff8103bd5a>] ? warn_slowpath_common+0x98/0xb0
[ 2.196098] [<ffffffffa00c96f0>] ? check_crtc_state+0xb67/0xbd1 [i915]
[ 2.196101] [<ffffffff8103bdb7>] ? warn_slowpath_fmt+0x45/0x4a
[ 2.196153] [<ffffffffa00c96f0>] ? check_crtc_state+0xb67/0xbd1 [i915]
[ 2.196208] [<ffffffffa00d85ba>] ? intel_modeset_check_state+0x610/0x9e9
[i915]
[ 2.196261] [<ffffffffa00d990f>] ? intel_crtc_set_config+0x986/0xc19 [i915]
[ 2.196275] [<ffffffffa000c314>] ? drm_mode_set_config_internal+0x4e/0xd2
[drm]
[ 2.196280] [<ffffffffa0058f89>] ? restore_fbdev_mode+0xac/0xc3
[drm_kms_helper]
[ 2.196285] [<ffffffffa005a78a>] ?
drm_fb_helper_restore_fbdev_mode_unlocked+0x1e/0x54 [drm_kms_helper]
[ 2.196290] [<ffffffffa005a7ee>] ? drm_fb_helper_set_par+0x2e/0x32
[drm_kms_helper]
[ 2.196342] [<ffffffffa00e5bab>] ? intel_fbdev_set_par+0x11/0x55 [i915]
[ 2.196347] [<ffffffff81374396>] ? fbcon_init+0x2fd/0x406
[ 2.196351] [<ffffffff813c9903>] ? visual_init+0xaf/0x102
[ 2.196355] [<ffffffff813caee9>] ? do_bind_con_driver+0x19e/0x2c2
[ 2.196358] [<ffffffff813cb476>] ? do_take_over_console+0x127/0x157
[ 2.196361] [<ffffffff81373a85>] ? do_fbcon_takeover+0x53/0x97
[ 2.196365] [<ffffffff81051620>] ? notifier_call_chain+0x35/0x59
[ 2.196368] [<ffffffff81051867>] ? __blocking_notifier_call_chain+0x43/0x5b
[ 2.196371] [<ffffffff8137bb13>] ? lock_fb_info+0x12/0x2f
[ 2.196374] [<ffffffff8137d32e>] ? register_framebuffer+0x26c/0x2a2
[ 2.196379] [<ffffffffa005aa9f>] ? drm_fb_helper_initial_config+0x2ad/0x34a
[drm_kms_helper]
[ 2.196383] [<ffffffff81052783>] ? async_run_entry_fn+0x2d/0xbf
[ 2.196387] [<ffffffff8104ca7f>] ? process_one_work+0x1b2/0x31d
[ 2.196390] [<ffffffff8104d278>] ? worker_thread+0x24d/0x339
[ 2.196393] [<ffffffff8104d02b>] ? cancel_delayed_work_sync+0xa/0xa
[ 2.196396] [<ffffffff81050b25>] ? kthread+0xce/0xd6
[ 2.196399] [<ffffffff81050a57>] ? kthread_create_on_node+0x162/0x162
[ 2.196402] [<ffffffff8179b048>] ? ret_from_fork+0x58/0x90
[ 2.196405] [<ffffffff81050a57>] ? kthread_create_on_node+0x162/0x162
[ 2.196407] ---[ end trace c9fd7503f7c341d1 ]---
==Reproduce steps==
----------------------------
1, connect the HDMI screen
2, start up the machine
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150417/48e9b462/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list