Hi,
linux-next 20150501
[ 1.968953] [drm:check_crtc_state [i915]] *ERROR* mismatch in scaler_state.scaler_id (expected 0, found -1) [ 1.968953] ------------[ cut here ]------------ [ 1.968983] WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:12008 check_crtc_state+0xb15/0xb83 [i915]() [ 1.968983] pipe state doesn't match! [..] [ 1.969005] CPU: 0 PID: 6 Comm: kworker/u16:0 Not tainted 4.1.0-rc1-next-20150501-dbg-00011-gbcb7bed-dirty #49 [ 1.969010] Workqueue: events_unbound async_run_entry_fn [ 1.969012] 0000000000000009 ffff88041d9eb448 ffffffff812e9753 0000000000005555 [ 1.969013] ffff88041d9eb498 ffff88041d9eb488 ffffffff81034c24 ffff88041d9eb490 [ 1.969015] ffffffffa03a81dc ffff88041d123000 ffff88041cbbc800 0000000000000001 [ 1.969015] Call Trace: [ 1.969019] [<ffffffff812e9753>] dump_stack+0x45/0x57 [ 1.969022] [<ffffffff81034c24>] warn_slowpath_common+0x97/0xb1 [ 1.969050] [<ffffffffa03a81dc>] ? check_crtc_state+0xb15/0xb83 [i915] [ 1.969052] [<ffffffff81034c7f>] warn_slowpath_fmt+0x41/0x43 [ 1.969080] [<ffffffffa03a81dc>] check_crtc_state+0xb15/0xb83 [i915] [ 1.969082] [<ffffffff81054941>] ? update_curr+0x68/0xd1 [ 1.969112] [<ffffffffa03b6ab6>] intel_modeset_check_state+0x603/0xa3d [i915] [ 1.969140] [<ffffffffa03b7db5>] intel_crtc_set_config+0x8dc/0xc02 [i915] [ 1.969147] [<ffffffffa0310d51>] ? drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] [ 1.969159] [<ffffffffa02688d2>] drm_mode_set_config_internal+0x57/0xe3 [drm] [ 1.969164] [<ffffffffa03122fa>] restore_fbdev_mode+0xb5/0xcf [drm_kms_helper] [ 1.969169] [<ffffffffa0313bb3>] drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] [ 1.969173] [<ffffffffa0313c1b>] drm_fb_helper_set_par+0x31/0x35 [drm_kms_helper] [ 1.969202] [<ffffffffa03c4151>] intel_fbdev_set_par+0x15/0x58 [i915] [ 1.969204] [<ffffffff811a3577>] fbcon_init+0x323/0x431 [ 1.969206] [<ffffffff811ef80a>] visual_init+0xb7/0x10d [ 1.969208] [<ffffffff811f0e26>] do_bind_con_driver+0x1b1/0x2d8 [ 1.969209] [<ffffffff811f124f>] do_take_over_console+0x15a/0x184 [ 1.969212] [<ffffffff811a15e7>] do_fbcon_takeover+0x5b/0x97 [ 1.969213] [<ffffffff811a4dc5>] fbcon_event_notify+0x419/0x740 [ 1.969215] [<ffffffff810492cc>] notifier_call_chain+0x3b/0x5f [ 1.969217] [<ffffffff8104950a>] __blocking_notifier_call_chain+0x43/0x5f [ 1.969219] [<ffffffff81049535>] blocking_notifier_call_chain+0xf/0x11 [ 1.969220] [<ffffffff811a68f8>] fb_notifier_call_chain+0x16/0x18 [ 1.969222] [<ffffffff811a8134>] register_framebuffer+0x28f/0x2c7 [ 1.969250] [<ffffffffa03c45a3>] ? intelfb_create+0x2e7/0x38a [i915] [ 1.969256] [<ffffffffa0313eb6>] drm_fb_helper_initial_config+0x297/0x3e1 [drm_kms_helper] [ 1.969284] [<ffffffffa03c4a9a>] intel_fbdev_initial_config+0x16/0x18 [i915] [ 1.969286] [<ffffffff8104a177>] async_run_entry_fn+0x33/0xca [ 1.969288] [<ffffffff8104408c>] process_one_work+0x192/0x2a8 [ 1.969290] [<ffffffff81044be8>] worker_thread+0x266/0x34c [ 1.969291] [<ffffffff81044982>] ? rescuer_thread+0x276/0x276 [ 1.969293] [<ffffffff81048908>] kthread+0xcd/0xd5 [ 1.969294] [<ffffffff8104883b>] ? kthread_worker_fn+0x130/0x130 [ 1.969296] [<ffffffff812ed5c2>] ret_from_fork+0x42/0x70 [ 1.969297] [<ffffffff8104883b>] ? kthread_worker_fn+0x130/0x130 [ 1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]---
-ss
Adding Chandra, who's implemented skl scaler code. -Daniel
On Sat, May 02, 2015 at 10:05:42AM +0900, Sergey Senozhatsky wrote:
Hi,
linux-next 20150501
[ 1.968953] [drm:check_crtc_state [i915]] *ERROR* mismatch in scaler_state.scaler_id (expected 0, found -1) [ 1.968953] ------------[ cut here ]------------ [ 1.968983] WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:12008 check_crtc_state+0xb15/0xb83 [i915]() [ 1.968983] pipe state doesn't match! [..] [ 1.969005] CPU: 0 PID: 6 Comm: kworker/u16:0 Not tainted 4.1.0-rc1-next-20150501-dbg-00011-gbcb7bed-dirty #49 [ 1.969010] Workqueue: events_unbound async_run_entry_fn [ 1.969012] 0000000000000009 ffff88041d9eb448 ffffffff812e9753 0000000000005555 [ 1.969013] ffff88041d9eb498 ffff88041d9eb488 ffffffff81034c24 ffff88041d9eb490 [ 1.969015] ffffffffa03a81dc ffff88041d123000 ffff88041cbbc800 0000000000000001 [ 1.969015] Call Trace: [ 1.969019] [<ffffffff812e9753>] dump_stack+0x45/0x57 [ 1.969022] [<ffffffff81034c24>] warn_slowpath_common+0x97/0xb1 [ 1.969050] [<ffffffffa03a81dc>] ? check_crtc_state+0xb15/0xb83 [i915] [ 1.969052] [<ffffffff81034c7f>] warn_slowpath_fmt+0x41/0x43 [ 1.969080] [<ffffffffa03a81dc>] check_crtc_state+0xb15/0xb83 [i915] [ 1.969082] [<ffffffff81054941>] ? update_curr+0x68/0xd1 [ 1.969112] [<ffffffffa03b6ab6>] intel_modeset_check_state+0x603/0xa3d [i915] [ 1.969140] [<ffffffffa03b7db5>] intel_crtc_set_config+0x8dc/0xc02 [i915] [ 1.969147] [<ffffffffa0310d51>] ? drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] [ 1.969159] [<ffffffffa02688d2>] drm_mode_set_config_internal+0x57/0xe3 [drm] [ 1.969164] [<ffffffffa03122fa>] restore_fbdev_mode+0xb5/0xcf [drm_kms_helper] [ 1.969169] [<ffffffffa0313bb3>] drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] [ 1.969173] [<ffffffffa0313c1b>] drm_fb_helper_set_par+0x31/0x35 [drm_kms_helper] [ 1.969202] [<ffffffffa03c4151>] intel_fbdev_set_par+0x15/0x58 [i915] [ 1.969204] [<ffffffff811a3577>] fbcon_init+0x323/0x431 [ 1.969206] [<ffffffff811ef80a>] visual_init+0xb7/0x10d [ 1.969208] [<ffffffff811f0e26>] do_bind_con_driver+0x1b1/0x2d8 [ 1.969209] [<ffffffff811f124f>] do_take_over_console+0x15a/0x184 [ 1.969212] [<ffffffff811a15e7>] do_fbcon_takeover+0x5b/0x97 [ 1.969213] [<ffffffff811a4dc5>] fbcon_event_notify+0x419/0x740 [ 1.969215] [<ffffffff810492cc>] notifier_call_chain+0x3b/0x5f [ 1.969217] [<ffffffff8104950a>] __blocking_notifier_call_chain+0x43/0x5f [ 1.969219] [<ffffffff81049535>] blocking_notifier_call_chain+0xf/0x11 [ 1.969220] [<ffffffff811a68f8>] fb_notifier_call_chain+0x16/0x18 [ 1.969222] [<ffffffff811a8134>] register_framebuffer+0x28f/0x2c7 [ 1.969250] [<ffffffffa03c45a3>] ? intelfb_create+0x2e7/0x38a [i915] [ 1.969256] [<ffffffffa0313eb6>] drm_fb_helper_initial_config+0x297/0x3e1 [drm_kms_helper] [ 1.969284] [<ffffffffa03c4a9a>] intel_fbdev_initial_config+0x16/0x18 [i915] [ 1.969286] [<ffffffff8104a177>] async_run_entry_fn+0x33/0xca [ 1.969288] [<ffffffff8104408c>] process_one_work+0x192/0x2a8 [ 1.969290] [<ffffffff81044be8>] worker_thread+0x266/0x34c [ 1.969291] [<ffffffff81044982>] ? rescuer_thread+0x276/0x276 [ 1.969293] [<ffffffff81048908>] kthread+0xcd/0xd5 [ 1.969294] [<ffffffff8104883b>] ? kthread_worker_fn+0x130/0x130 [ 1.969296] [<ffffffff812ed5c2>] ret_from_fork+0x42/0x70 [ 1.969297] [<ffffffff8104883b>] ? kthread_worker_fn+0x130/0x130 [ 1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]---
-ss _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi, This error happens when crtc_state in driver not matching with hardware registers. On skylake board that I have, I am not able to reproduce the issue. Can you send the system configuration and steps to reproduce the issue? Also can you send the full dmesg.log file?
-Chandra
-----Original Message----- From: Daniel Vetter [mailto:daniel.vetter@ffwll.ch] On Behalf Of Daniel Vetter Sent: Wednesday, May 06, 2015 4:09 AM To: Sergey Senozhatsky Cc: David Airlie; Vetter, Daniel; intel-gfx@lists.freedesktop.org; dri- devel@lists.freedesktop.org; linux-kernel@vger.kernel.org; Konduru, Chandra Subject: Re: [i915]] *ERROR* mismatch in scaler_state.scaler_id
Adding Chandra, who's implemented skl scaler code. -Daniel
On Sat, May 02, 2015 at 10:05:42AM +0900, Sergey Senozhatsky wrote:
Hi,
linux-next 20150501
[ 1.968953] [drm:check_crtc_state [i915]] *ERROR* mismatch in
scaler_state.scaler_id (expected 0, found -1)
[ 1.968953] ------------[ cut here ]------------ [ 1.968983] WARNING: CPU: 0 PID: 6 at
drivers/gpu/drm/i915/intel_display.c:12008 check_crtc_state+0xb15/0xb83 [i915]()
[ 1.968983] pipe state doesn't match! [..] [ 1.969005] CPU: 0 PID: 6 Comm: kworker/u16:0 Not tainted 4.1.0-rc1-next-
20150501-dbg-00011-gbcb7bed-dirty #49
[ 1.969010] Workqueue: events_unbound async_run_entry_fn [ 1.969012] 0000000000000009 ffff88041d9eb448 ffffffff812e9753
0000000000005555
[ 1.969013] ffff88041d9eb498 ffff88041d9eb488 ffffffff81034c24
ffff88041d9eb490
[ 1.969015] ffffffffa03a81dc ffff88041d123000 ffff88041cbbc800
0000000000000001
[ 1.969015] Call Trace: [ 1.969019] [<ffffffff812e9753>] dump_stack+0x45/0x57 [ 1.969022] [<ffffffff81034c24>] warn_slowpath_common+0x97/0xb1 [ 1.969050] [<ffffffffa03a81dc>] ? check_crtc_state+0xb15/0xb83 [i915] [ 1.969052] [<ffffffff81034c7f>] warn_slowpath_fmt+0x41/0x43 [ 1.969080] [<ffffffffa03a81dc>] check_crtc_state+0xb15/0xb83 [i915] [ 1.969082] [<ffffffff81054941>] ? update_curr+0x68/0xd1 [ 1.969112] [<ffffffffa03b6ab6>] intel_modeset_check_state+0x603/0xa3d
[i915]
[ 1.969140] [<ffffffffa03b7db5>] intel_crtc_set_config+0x8dc/0xc02 [i915] [ 1.969147] [<ffffffffa0310d51>] ?
drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper]
[ 1.969159] [<ffffffffa02688d2>] drm_mode_set_config_internal+0x57/0xe3
[drm]
[ 1.969164] [<ffffffffa03122fa>] restore_fbdev_mode+0xb5/0xcf
[drm_kms_helper]
[ 1.969169] [<ffffffffa0313bb3>]
drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper]
[ 1.969173] [<ffffffffa0313c1b>] drm_fb_helper_set_par+0x31/0x35
[drm_kms_helper]
[ 1.969202] [<ffffffffa03c4151>] intel_fbdev_set_par+0x15/0x58 [i915] [ 1.969204] [<ffffffff811a3577>] fbcon_init+0x323/0x431 [ 1.969206] [<ffffffff811ef80a>] visual_init+0xb7/0x10d [ 1.969208] [<ffffffff811f0e26>] do_bind_con_driver+0x1b1/0x2d8 [ 1.969209] [<ffffffff811f124f>] do_take_over_console+0x15a/0x184 [ 1.969212] [<ffffffff811a15e7>] do_fbcon_takeover+0x5b/0x97 [ 1.969213] [<ffffffff811a4dc5>] fbcon_event_notify+0x419/0x740 [ 1.969215] [<ffffffff810492cc>] notifier_call_chain+0x3b/0x5f [ 1.969217] [<ffffffff8104950a>] __blocking_notifier_call_chain+0x43/0x5f [ 1.969219] [<ffffffff81049535>] blocking_notifier_call_chain+0xf/0x11 [ 1.969220] [<ffffffff811a68f8>] fb_notifier_call_chain+0x16/0x18 [ 1.969222] [<ffffffff811a8134>] register_framebuffer+0x28f/0x2c7 [ 1.969250] [<ffffffffa03c45a3>] ? intelfb_create+0x2e7/0x38a [i915] [ 1.969256] [<ffffffffa0313eb6>] drm_fb_helper_initial_config+0x297/0x3e1
[drm_kms_helper]
[ 1.969284] [<ffffffffa03c4a9a>] intel_fbdev_initial_config+0x16/0x18
[i915]
[ 1.969286] [<ffffffff8104a177>] async_run_entry_fn+0x33/0xca [ 1.969288] [<ffffffff8104408c>] process_one_work+0x192/0x2a8 [ 1.969290] [<ffffffff81044be8>] worker_thread+0x266/0x34c [ 1.969291] [<ffffffff81044982>] ? rescuer_thread+0x276/0x276 [ 1.969293] [<ffffffff81048908>] kthread+0xcd/0xd5 [ 1.969294] [<ffffffff8104883b>] ? kthread_worker_fn+0x130/0x130 [ 1.969296] [<ffffffff812ed5c2>] ret_from_fork+0x42/0x70 [ 1.969297] [<ffffffff8104883b>] ? kthread_worker_fn+0x130/0x130 [ 1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]---
-ss _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
-- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
On (05/07/15 00:40), Konduru, Chandra wrote:
Hi, This error happens when crtc_state in driver not matching with hardware registers. On skylake board that I have, I am not able to reproduce the issue. Can you send the system configuration and steps to reproduce the issue? Also can you send the full dmesg.log file?
Hi, there are no specific steps, happens during boot and every time the screen goes unblank. attached dmesg, .config.
~$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d4) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM86 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1) 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 93) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
/* 01:00.0 3D controller: NVIDIA Corporation GK107M not used */
-ss
-----Original Message----- From: Sergey Senozhatsky [mailto:sergey.senozhatsky@gmail.com] Sent: Thursday, May 07, 2015 4:24 AM To: Konduru, Chandra Cc: Daniel Vetter; Sergey Senozhatsky; David Airlie; Vetter, Daniel; intel- gfx@lists.freedesktop.org; dri-devel@lists.freedesktop.org; linux- kernel@vger.kernel.org Subject: Re: [i915]] *ERROR* mismatch in scaler_state.scaler_id
On (05/07/15 00:40), Konduru, Chandra wrote:
Hi, This error happens when crtc_state in driver not matching with hardware
registers.
On skylake board that I have, I am not able to reproduce the issue. Can you send the system configuration and steps to reproduce the issue? Also can you send the full dmesg.log file?
Hi, there are no specific steps, happens during boot and every time the screen goes unblank. attached dmesg, .config.
OK, I am able reproduce the mismatch scaler id log on HSW system. Though, this log doesn't affect system functionality, but it is an unnecessary annoyance. This check is targeted for SKL and shouldn't happen for HSW. Submitted a patch to limit the check for skl+: http://patchwork.freedesktop.org/patch/48858/
On (05/08/15 01:27), Konduru, Chandra wrote:
there are no specific steps, happens during boot and every time the screen goes unblank. attached dmesg, .config.
OK, I am able reproduce the mismatch scaler id log on HSW system. Though, this log doesn't affect system functionality, but it is an unnecessary annoyance. This check is targeted for SKL and shouldn't happen for HSW. Submitted a patch to limit the check for skl+: http://patchwork.freedesktop.org/patch/48858/
jfi, the usual patch exchange happens in mailing lists. `git am <email>' vs. `browsing some pages and downloading attached patches'.
back to the patch: no more mismatch warnings.
Reported-and-tested-by: Sergey Senozhatsky sergey.senozhatsky@gmail.com
-ss
dri-devel@lists.freedesktop.org
-
Daniel Vetter -
Konduru, Chandra -
Sergey Senozhatsky