Re: [i915]] *ERROR* mismatch in scaler_state.scaler_id
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 ' vs. `browsing some pages and downloading attached patches'. back to the patch: no more mismatch warnings. Reported-and-tested-by: Sergey Senozhatsky -ss -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [i915]] *ERROR* mismatch in scaler_state.scaler_id
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.senozhat...@gmail.com -ss -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [i915]] *ERROR* mismatch in scaler_state.scaler_id
> -Original Message- > From: Sergey Senozhatsky [mailto:sergey.senozhat...@gmail.com] > Sent: Thursday, May 07, 2015 4:24 AM > To: Konduru, Chandra > Cc: Daniel Vetter; Sergey Senozhatsky; David Airlie; Vetter, Daniel; intel- > g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; linux- > ker...@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/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [i915]] *ERROR* mismatch in scaler_state.scaler_id
-Original Message- From: Sergey Senozhatsky [mailto:sergey.senozhat...@gmail.com] Sent: Thursday, May 07, 2015 4:24 AM To: Konduru, Chandra Cc: Daniel Vetter; Sergey Senozhatsky; David Airlie; Vetter, Daniel; intel- g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org; linux- ker...@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/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [i915]] *ERROR* mismatch in scaler_state.scaler_id
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.vet...@ffwll.ch] On Behalf Of Daniel Vetter > Sent: Wednesday, May 06, 2015 4:09 AM > To: Sergey Senozhatsky > Cc: David Airlie; Vetter, Daniel; intel-...@lists.freedesktop.org; dri- > de...@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] 0009 88041d9eb448 812e9753 > > > [1.969013] 88041d9eb498 88041d9eb488 81034c24 > 88041d9eb490 > > [1.969015] a03a81dc 88041d123000 88041cbbc800 > 0001 > > [1.969015] Call Trace: > > [1.969019] [] dump_stack+0x45/0x57 > > [1.969022] [] warn_slowpath_common+0x97/0xb1 > > [1.969050] [] ? check_crtc_state+0xb15/0xb83 [i915] > > [1.969052] [] warn_slowpath_fmt+0x41/0x43 > > [1.969080] [] check_crtc_state+0xb15/0xb83 [i915] > > [1.969082] [] ? update_curr+0x68/0xd1 > > [1.969112] [] intel_modeset_check_state+0x603/0xa3d > [i915] > > [1.969140] [] intel_crtc_set_config+0x8dc/0xc02 > > [i915] > > [1.969147] [] ? > drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] > > [1.969159] [] drm_mode_set_config_internal+0x57/0xe3 > [drm] > > [1.969164] [] restore_fbdev_mode+0xb5/0xcf > [drm_kms_helper] > > [1.969169] [] > drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] > > [1.969173] [] drm_fb_helper_set_par+0x31/0x35 > [drm_kms_helper] > > [1.969202] [] intel_fbdev_set_par+0x15/0x58 [i915] > > [1.969204] [] fbcon_init+0x323/0x431 > > [1.969206] [] visual_init+0xb7/0x10d > > [1.969208] [] do_bind_con_driver+0x1b1/0x2d8 > > [1.969209] [] do_take_over_console+0x15a/0x184 > > [1.969212] [] do_fbcon_takeover+0x5b/0x97 > > [1.969213] [] fbcon_event_notify+0x419/0x740 > > [1.969215] [] notifier_call_chain+0x3b/0x5f > > [1.969217] [] > > __blocking_notifier_call_chain+0x43/0x5f > > [1.969219] [] blocking_notifier_call_chain+0xf/0x11 > > [1.969220] [] fb_notifier_call_chain+0x16/0x18 > > [1.969222] [] register_framebuffer+0x28f/0x2c7 > > [1.969250] [] ? intelfb_create+0x2e7/0x38a [i915] > > [1.969256] [] > > drm_fb_helper_initial_config+0x297/0x3e1 > [drm_kms_helper] > > [1.969284] [] intel_fbdev_initial_config+0x16/0x18 > [i915] > > [1.969286] [] async_run_entry_fn+0x33/0xca > > [1.969288] [] process_one_work+0x192/0x2a8 > > [1.969290] [] worker_thread+0x266/0x34c > > [1.969291] [] ? rescuer_thread+0x276/0x276 > > [1.969293] [] kthread+0xcd/0xd5 > > [1.969294] [] ? kthread_worker_fn+0x130/0x130 > > [1.969296] [] ret_from_fork+0x42/0x70 > > [1.969297] [] ? kthread_worker_fn+0x130/0x130 > > [1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]--- > > > > -ss > > ___ > > dri-devel mailing list > > dri-de...@lists.freedesktop.org > > http://lists.freedesktop.org/mailman/listinfo/dri-devel > > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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] 0009 88041d9eb448 812e9753 > > [1.969013] 88041d9eb498 88041d9eb488 81034c24 > 88041d9eb490 > [1.969015] a03a81dc 88041d123000 88041cbbc800 > 0001 > [1.969015] Call Trace: > [1.969019] [] dump_stack+0x45/0x57 > [1.969022] [] warn_slowpath_common+0x97/0xb1 > [1.969050] [] ? check_crtc_state+0xb15/0xb83 [i915] > [1.969052] [] warn_slowpath_fmt+0x41/0x43 > [1.969080] [] check_crtc_state+0xb15/0xb83 [i915] > [1.969082] [] ? update_curr+0x68/0xd1 > [1.969112] [] intel_modeset_check_state+0x603/0xa3d > [i915] > [1.969140] [] intel_crtc_set_config+0x8dc/0xc02 [i915] > [1.969147] [] ? > drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] > [1.969159] [] drm_mode_set_config_internal+0x57/0xe3 > [drm] > [1.969164] [] restore_fbdev_mode+0xb5/0xcf > [drm_kms_helper] > [1.969169] [] > drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] > [1.969173] [] drm_fb_helper_set_par+0x31/0x35 > [drm_kms_helper] > [1.969202] [] intel_fbdev_set_par+0x15/0x58 [i915] > [1.969204] [] fbcon_init+0x323/0x431 > [1.969206] [] visual_init+0xb7/0x10d > [1.969208] [] do_bind_con_driver+0x1b1/0x2d8 > [1.969209] [] do_take_over_console+0x15a/0x184 > [1.969212] [] do_fbcon_takeover+0x5b/0x97 > [1.969213] [] fbcon_event_notify+0x419/0x740 > [1.969215] [] notifier_call_chain+0x3b/0x5f > [1.969217] [] __blocking_notifier_call_chain+0x43/0x5f > [1.969219] [] blocking_notifier_call_chain+0xf/0x11 > [1.969220] [] fb_notifier_call_chain+0x16/0x18 > [1.969222] [] register_framebuffer+0x28f/0x2c7 > [1.969250] [] ? intelfb_create+0x2e7/0x38a [i915] > [1.969256] [] drm_fb_helper_initial_config+0x297/0x3e1 > [drm_kms_helper] > [1.969284] [] intel_fbdev_initial_config+0x16/0x18 > [i915] > [1.969286] [] async_run_entry_fn+0x33/0xca > [1.969288] [] process_one_work+0x192/0x2a8 > [1.969290] [] worker_thread+0x266/0x34c > [1.969291] [] ? rescuer_thread+0x276/0x276 > [1.969293] [] kthread+0xcd/0xd5 > [1.969294] [] ? kthread_worker_fn+0x130/0x130 > [1.969296] [] ret_from_fork+0x42/0x70 > [1.969297] [] ? kthread_worker_fn+0x130/0x130 > [1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]--- > > -ss > ___ > dri-devel mailing list > dri-de...@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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] 0009 88041d9eb448 812e9753 [1.969013] 88041d9eb498 88041d9eb488 81034c24 88041d9eb490 [1.969015] a03a81dc 88041d123000 88041cbbc800 0001 [1.969015] Call Trace: [1.969019] [812e9753] dump_stack+0x45/0x57 [1.969022] [81034c24] warn_slowpath_common+0x97/0xb1 [1.969050] [a03a81dc] ? check_crtc_state+0xb15/0xb83 [i915] [1.969052] [81034c7f] warn_slowpath_fmt+0x41/0x43 [1.969080] [a03a81dc] check_crtc_state+0xb15/0xb83 [i915] [1.969082] [81054941] ? update_curr+0x68/0xd1 [1.969112] [a03b6ab6] intel_modeset_check_state+0x603/0xa3d [i915] [1.969140] [a03b7db5] intel_crtc_set_config+0x8dc/0xc02 [i915] [1.969147] [a0310d51] ? drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] [1.969159] [a02688d2] drm_mode_set_config_internal+0x57/0xe3 [drm] [1.969164] [a03122fa] restore_fbdev_mode+0xb5/0xcf [drm_kms_helper] [1.969169] [a0313bb3] drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] [1.969173] [a0313c1b] drm_fb_helper_set_par+0x31/0x35 [drm_kms_helper] [1.969202] [a03c4151] intel_fbdev_set_par+0x15/0x58 [i915] [1.969204] [811a3577] fbcon_init+0x323/0x431 [1.969206] [811ef80a] visual_init+0xb7/0x10d [1.969208] [811f0e26] do_bind_con_driver+0x1b1/0x2d8 [1.969209] [811f124f] do_take_over_console+0x15a/0x184 [1.969212] [811a15e7] do_fbcon_takeover+0x5b/0x97 [1.969213] [811a4dc5] fbcon_event_notify+0x419/0x740 [1.969215] [810492cc] notifier_call_chain+0x3b/0x5f [1.969217] [8104950a] __blocking_notifier_call_chain+0x43/0x5f [1.969219] [81049535] blocking_notifier_call_chain+0xf/0x11 [1.969220] [811a68f8] fb_notifier_call_chain+0x16/0x18 [1.969222] [811a8134] register_framebuffer+0x28f/0x2c7 [1.969250] [a03c45a3] ? intelfb_create+0x2e7/0x38a [i915] [1.969256] [a0313eb6] drm_fb_helper_initial_config+0x297/0x3e1 [drm_kms_helper] [1.969284] [a03c4a9a] intel_fbdev_initial_config+0x16/0x18 [i915] [1.969286] [8104a177] async_run_entry_fn+0x33/0xca [1.969288] [8104408c] process_one_work+0x192/0x2a8 [1.969290] [81044be8] worker_thread+0x266/0x34c [1.969291] [81044982] ? rescuer_thread+0x276/0x276 [1.969293] [81048908] kthread+0xcd/0xd5 [1.969294] [8104883b] ? kthread_worker_fn+0x130/0x130 [1.969296] [812ed5c2] ret_from_fork+0x42/0x70 [1.969297] [8104883b] ? kthread_worker_fn+0x130/0x130 [1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]--- -ss ___ dri-devel mailing list dri-de...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [i915]] *ERROR* mismatch in scaler_state.scaler_id
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.vet...@ffwll.ch] On Behalf Of Daniel Vetter Sent: Wednesday, May 06, 2015 4:09 AM To: Sergey Senozhatsky Cc: David Airlie; Vetter, Daniel; intel-...@lists.freedesktop.org; dri- de...@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] 0009 88041d9eb448 812e9753 [1.969013] 88041d9eb498 88041d9eb488 81034c24 88041d9eb490 [1.969015] a03a81dc 88041d123000 88041cbbc800 0001 [1.969015] Call Trace: [1.969019] [812e9753] dump_stack+0x45/0x57 [1.969022] [81034c24] warn_slowpath_common+0x97/0xb1 [1.969050] [a03a81dc] ? check_crtc_state+0xb15/0xb83 [i915] [1.969052] [81034c7f] warn_slowpath_fmt+0x41/0x43 [1.969080] [a03a81dc] check_crtc_state+0xb15/0xb83 [i915] [1.969082] [81054941] ? update_curr+0x68/0xd1 [1.969112] [a03b6ab6] intel_modeset_check_state+0x603/0xa3d [i915] [1.969140] [a03b7db5] intel_crtc_set_config+0x8dc/0xc02 [i915] [1.969147] [a0310d51] ? drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] [1.969159] [a02688d2] drm_mode_set_config_internal+0x57/0xe3 [drm] [1.969164] [a03122fa] restore_fbdev_mode+0xb5/0xcf [drm_kms_helper] [1.969169] [a0313bb3] drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] [1.969173] [a0313c1b] drm_fb_helper_set_par+0x31/0x35 [drm_kms_helper] [1.969202] [a03c4151] intel_fbdev_set_par+0x15/0x58 [i915] [1.969204] [811a3577] fbcon_init+0x323/0x431 [1.969206] [811ef80a] visual_init+0xb7/0x10d [1.969208] [811f0e26] do_bind_con_driver+0x1b1/0x2d8 [1.969209] [811f124f] do_take_over_console+0x15a/0x184 [1.969212] [811a15e7] do_fbcon_takeover+0x5b/0x97 [1.969213] [811a4dc5] fbcon_event_notify+0x419/0x740 [1.969215] [810492cc] notifier_call_chain+0x3b/0x5f [1.969217] [8104950a] __blocking_notifier_call_chain+0x43/0x5f [1.969219] [81049535] blocking_notifier_call_chain+0xf/0x11 [1.969220] [811a68f8] fb_notifier_call_chain+0x16/0x18 [1.969222] [811a8134] register_framebuffer+0x28f/0x2c7 [1.969250] [a03c45a3] ? intelfb_create+0x2e7/0x38a [i915] [1.969256] [a0313eb6] drm_fb_helper_initial_config+0x297/0x3e1 [drm_kms_helper] [1.969284] [a03c4a9a] intel_fbdev_initial_config+0x16/0x18 [i915] [1.969286] [8104a177] async_run_entry_fn+0x33/0xca [1.969288] [8104408c] process_one_work+0x192/0x2a8 [1.969290] [81044be8] worker_thread+0x266/0x34c [1.969291] [81044982] ? rescuer_thread+0x276/0x276 [1.969293] [81048908] kthread+0xcd/0xd5 [1.969294] [8104883b] ? kthread_worker_fn+0x130/0x130 [1.969296] [812ed5c2] ret_from_fork+0x42/0x70 [1.969297] [8104883b] ? kthread_worker_fn+0x130/0x130 [1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]--- -ss ___ dri-devel mailing list dri-de...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[i915]] *ERROR* mismatch in scaler_state.scaler_id
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] 0009 88041d9eb448 812e9753 [1.969013] 88041d9eb498 88041d9eb488 81034c24 88041d9eb490 [1.969015] a03a81dc 88041d123000 88041cbbc800 0001 [1.969015] Call Trace: [1.969019] [] dump_stack+0x45/0x57 [1.969022] [] warn_slowpath_common+0x97/0xb1 [1.969050] [] ? check_crtc_state+0xb15/0xb83 [i915] [1.969052] [] warn_slowpath_fmt+0x41/0x43 [1.969080] [] check_crtc_state+0xb15/0xb83 [i915] [1.969082] [] ? update_curr+0x68/0xd1 [1.969112] [] intel_modeset_check_state+0x603/0xa3d [i915] [1.969140] [] intel_crtc_set_config+0x8dc/0xc02 [i915] [1.969147] [] ? drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] [1.969159] [] drm_mode_set_config_internal+0x57/0xe3 [drm] [1.969164] [] restore_fbdev_mode+0xb5/0xcf [drm_kms_helper] [1.969169] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] [1.969173] [] drm_fb_helper_set_par+0x31/0x35 [drm_kms_helper] [1.969202] [] intel_fbdev_set_par+0x15/0x58 [i915] [1.969204] [] fbcon_init+0x323/0x431 [1.969206] [] visual_init+0xb7/0x10d [1.969208] [] do_bind_con_driver+0x1b1/0x2d8 [1.969209] [] do_take_over_console+0x15a/0x184 [1.969212] [] do_fbcon_takeover+0x5b/0x97 [1.969213] [] fbcon_event_notify+0x419/0x740 [1.969215] [] notifier_call_chain+0x3b/0x5f [1.969217] [] __blocking_notifier_call_chain+0x43/0x5f [1.969219] [] blocking_notifier_call_chain+0xf/0x11 [1.969220] [] fb_notifier_call_chain+0x16/0x18 [1.969222] [] register_framebuffer+0x28f/0x2c7 [1.969250] [] ? intelfb_create+0x2e7/0x38a [i915] [1.969256] [] drm_fb_helper_initial_config+0x297/0x3e1 [drm_kms_helper] [1.969284] [] intel_fbdev_initial_config+0x16/0x18 [i915] [1.969286] [] async_run_entry_fn+0x33/0xca [1.969288] [] process_one_work+0x192/0x2a8 [1.969290] [] worker_thread+0x266/0x34c [1.969291] [] ? rescuer_thread+0x276/0x276 [1.969293] [] kthread+0xcd/0xd5 [1.969294] [] ? kthread_worker_fn+0x130/0x130 [1.969296] [] ret_from_fork+0x42/0x70 [1.969297] [] ? kthread_worker_fn+0x130/0x130 [1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]--- -ss -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[i915]] *ERROR* mismatch in scaler_state.scaler_id
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] 0009 88041d9eb448 812e9753 [1.969013] 88041d9eb498 88041d9eb488 81034c24 88041d9eb490 [1.969015] a03a81dc 88041d123000 88041cbbc800 0001 [1.969015] Call Trace: [1.969019] [812e9753] dump_stack+0x45/0x57 [1.969022] [81034c24] warn_slowpath_common+0x97/0xb1 [1.969050] [a03a81dc] ? check_crtc_state+0xb15/0xb83 [i915] [1.969052] [81034c7f] warn_slowpath_fmt+0x41/0x43 [1.969080] [a03a81dc] check_crtc_state+0xb15/0xb83 [i915] [1.969082] [81054941] ? update_curr+0x68/0xd1 [1.969112] [a03b6ab6] intel_modeset_check_state+0x603/0xa3d [i915] [1.969140] [a03b7db5] intel_crtc_set_config+0x8dc/0xc02 [i915] [1.969147] [a0310d51] ? drm_atomic_helper_plane_set_property+0x6c/0xa4 [drm_kms_helper] [1.969159] [a02688d2] drm_mode_set_config_internal+0x57/0xe3 [drm] [1.969164] [a03122fa] restore_fbdev_mode+0xb5/0xcf [drm_kms_helper] [1.969169] [a0313bb3] drm_fb_helper_restore_fbdev_mode_unlocked+0x22/0x59 [drm_kms_helper] [1.969173] [a0313c1b] drm_fb_helper_set_par+0x31/0x35 [drm_kms_helper] [1.969202] [a03c4151] intel_fbdev_set_par+0x15/0x58 [i915] [1.969204] [811a3577] fbcon_init+0x323/0x431 [1.969206] [811ef80a] visual_init+0xb7/0x10d [1.969208] [811f0e26] do_bind_con_driver+0x1b1/0x2d8 [1.969209] [811f124f] do_take_over_console+0x15a/0x184 [1.969212] [811a15e7] do_fbcon_takeover+0x5b/0x97 [1.969213] [811a4dc5] fbcon_event_notify+0x419/0x740 [1.969215] [810492cc] notifier_call_chain+0x3b/0x5f [1.969217] [8104950a] __blocking_notifier_call_chain+0x43/0x5f [1.969219] [81049535] blocking_notifier_call_chain+0xf/0x11 [1.969220] [811a68f8] fb_notifier_call_chain+0x16/0x18 [1.969222] [811a8134] register_framebuffer+0x28f/0x2c7 [1.969250] [a03c45a3] ? intelfb_create+0x2e7/0x38a [i915] [1.969256] [a0313eb6] drm_fb_helper_initial_config+0x297/0x3e1 [drm_kms_helper] [1.969284] [a03c4a9a] intel_fbdev_initial_config+0x16/0x18 [i915] [1.969286] [8104a177] async_run_entry_fn+0x33/0xca [1.969288] [8104408c] process_one_work+0x192/0x2a8 [1.969290] [81044be8] worker_thread+0x266/0x34c [1.969291] [81044982] ? rescuer_thread+0x276/0x276 [1.969293] [81048908] kthread+0xcd/0xd5 [1.969294] [8104883b] ? kthread_worker_fn+0x130/0x130 [1.969296] [812ed5c2] ret_from_fork+0x42/0x70 [1.969297] [8104883b] ? kthread_worker_fn+0x130/0x130 [1.969298] ---[ end trace 7f37d8e5ab4ee0a8 ]--- -ss -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
