Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1220359 > unrolled thread

Re: [git pull] drm for 4.3

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [git pull] drm for 4.3 Dave Jones <davej@codemonkey.org.uk> - 2015-09-07 20:50 +0200
    Re: [git pull] drm for 4.3 Dave Jones <davej@codemonkey.org.uk> - 2015-09-21 20:50 +0200
      Re: [Intel-gfx] [git pull] drm for 4.3 Jesse Barnes <jbarnes@virtuousgeek.org> - 2015-09-22 17:10 +0200
        [regression] [git pull] drm for 4.3 Daniel Vetter <daniel@ffwll.ch> - 2015-09-22 17:20 +0200
          Re: [regression] [git pull] drm for 4.3 Matt Roper <matthew.d.roper@intel.com> - 2015-09-22 18:20 +0200
            Re: [regression] [git pull] drm for 4.3 Dave Jones <davej@codemonkey.org.uk> - 2015-09-23 03:50 +0200
              Re: [regression] [git pull] drm for 4.3 "Lankhorst, Maarten" <maarten.lankhorst@intel.com> - 2015-09-23 13:10 +0200
                Re: [regression] [git pull] drm for 4.3 "davej@codemonkey.org.uk" <davej@codemonkey.org.uk> - 2015-09-24 06:00 +0200
                  Re: [regression] [git pull] drm for 4.3 Jani Nikula <jani.nikula@linux.intel.com> - 2015-09-24 15:30 +0200
                    Re: [regression] [git pull] drm for 4.3 "davej@codemonkey.org.uk" <davej@codemonkey.org.uk> - 2015-09-30 03:10 +0200
                      Re: [regression] [git pull] drm for 4.3 Daniel Vetter <daniel@ffwll.ch> - 2015-09-30 09:00 +0200
                  [Intel-gfx] [regression] boot to the blackscreen with the kernel 4.3 zhuhuachun <zhuhuachun@sinap.ac.cn> - 2015-09-29 09:00 +0200

#1220359 — Re: [git pull] drm for 4.3

On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
 > 
 > Hi Linus,
 > 
 > This is the main pull request for the drm for 4.3. Nouveau is probably the biggest
 > amount of changes in here, since it missed 4.2. Highlights below, along with the usual
 > bunch of fixes. There are a few minor conflicts with your tree but nothing 
 > you can't handle. All stuff outside drm should have applicable acks.
 > 
 > Highlights:
 > 
 > ...
 > i915:
 > 	Skylake support enabled by default
 > 	legacy modesetting using atomic infrastructure
 > 	Skylake fixes
 > 	GEN9 workarounds

Since this merge, I'm seeing this twice during boot..


------------[ cut here ]------------
WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:1377 assert_planes_disabled+0xdf/0x140()
plane A assertion failure, should be disabled but not
CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 4.2.0-think+ #9
Workqueue: events_unbound async_run_entry_fn
 0000000000000561 ffff88050392b6f8 ffffffff8d7dccce ffff88050392b740
 ffff88050392b730 ffffffff8d079ee2 ffff880500a60000 0000000000000000
 0000000000000000 0000000000000000 ffff8805008e99c8 ffff88050392b790
Call Trace:
 [<ffffffff8d7dccce>] dump_stack+0x4e/0x79
 [<ffffffff8d079ee2>] warn_slowpath_common+0x82/0xc0
 [<ffffffff8d079f6c>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffff8d4ee6ff>] assert_planes_disabled+0xdf/0x140
 [<ffffffff8d4f7b5b>] intel_disable_pipe+0x4b/0x2c0
 [<ffffffff8d4f7e5a>] haswell_crtc_disable+0x8a/0x2e0
 [<ffffffff8d500e7f>] intel_atomic_commit+0xff/0x1320
 [<ffffffff8d4885be>] ? drm_atomic_check_only+0x21e/0x550
 [<ffffffff8d488927>] drm_atomic_commit+0x37/0x60
 [<ffffffff8d463c95>] drm_atomic_helper_set_config+0x1c5/0x430
 [<ffffffff8d477c95>] drm_mode_set_config_internal+0x65/0x110
 [<ffffffff8d4666fe>] restore_fbdev_mode+0xbe/0xe0
 [<ffffffff8d468565>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
 [<ffffffff8d4685dd>] drm_fb_helper_set_par+0x2d/0x50
 [<ffffffff8d517a1a>] intel_fbdev_set_par+0x1a/0x60
 [<ffffffff8d3aeb45>] fbcon_init+0x545/0x5d0
 [<ffffffff8d42d68a>] visual_init+0xca/0x130
 [<ffffffff8d42f495>] do_bind_con_driver+0x1c5/0x3b0
 [<ffffffff8d42f9b9>] do_take_over_console+0x149/0x1a0
 [<ffffffff8d3aa9e7>] do_fbcon_takeover+0x57/0xb0
 [<ffffffff8d3af5ec>] fbcon_event_notify+0x66c/0x760
 [<ffffffff8d09e06e>] notifier_call_chain+0x3e/0xb0
 [<ffffffff8d09e26d>] __blocking_notifier_call_chain+0x4d/0x70
 [<ffffffff8d09e2a6>] blocking_notifier_call_chain+0x16/0x20
 [<ffffffff8d3b4d8b>] fb_notifier_call_chain+0x1b/0x20
 [<ffffffff8d3b7097>] register_framebuffer+0x1e7/0x300
 [<ffffffff8d468852>] drm_fb_helper_initial_config+0x252/0x3e0
 [<ffffffff8d5184cb>] intel_fbdev_initial_config+0x1b/0x20
 [<ffffffff8d0a02fa>] async_run_entry_fn+0x4a/0x140
 [<ffffffff8d09645d>] process_one_work+0x1fd/0x670
 [<ffffffff8d0963cc>] ? process_one_work+0x16c/0x670
 [<ffffffff8d09691e>] worker_thread+0x4e/0x450
 [<ffffffff8d0968d0>] ? process_one_work+0x670/0x670
 [<ffffffff8d09ccc1>] kthread+0x101/0x120
 [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
 [<ffffffff8d7e764f>] ret_from_fork+0x3f/0x70
 [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
---[ end trace 54cab2e0c772d5d9 ]---


00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller (rev 06)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1229647

On Mon, Sep 07, 2015 at 02:45:59PM -0400, Dave Jones wrote:
 > On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
 >  > 
 >  > Hi Linus,
 >  > 
 >  > This is the main pull request for the drm for 4.3. Nouveau is probably the biggest
 >  > amount of changes in here, since it missed 4.2. Highlights below, along with the usual
 >  > bunch of fixes. There are a few minor conflicts with your tree but nothing 
 >  > you can't handle. All stuff outside drm should have applicable acks.
 >  > 
 >  > Highlights:
 >  > 
 >  > ...
 >  > i915:
 >  > 	Skylake support enabled by default
 >  > 	legacy modesetting using atomic infrastructure
 >  > 	Skylake fixes
 >  > 	GEN9 workarounds
 > 
 > Since this merge, I'm seeing this twice during boot..

And still there in -rc2.  Several other people reported this too,
and they also got no reponse.

I'll start bisecting when I get home tonight. It shouldn't be too hard,
as 4.2 was fine.

	Dave

 > ------------[ cut here ]------------
 > WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:1377 assert_planes_disabled+0xdf/0x140()
 > plane A assertion failure, should be disabled but not
 > CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 4.2.0-think+ #9
 > Workqueue: events_unbound async_run_entry_fn
 >  0000000000000561 ffff88050392b6f8 ffffffff8d7dccce ffff88050392b740
 >  ffff88050392b730 ffffffff8d079ee2 ffff880500a60000 0000000000000000
 >  0000000000000000 0000000000000000 ffff8805008e99c8 ffff88050392b790
 > Call Trace:
 >  [<ffffffff8d7dccce>] dump_stack+0x4e/0x79
 >  [<ffffffff8d079ee2>] warn_slowpath_common+0x82/0xc0
 >  [<ffffffff8d079f6c>] warn_slowpath_fmt+0x4c/0x50
 >  [<ffffffff8d4ee6ff>] assert_planes_disabled+0xdf/0x140
 >  [<ffffffff8d4f7b5b>] intel_disable_pipe+0x4b/0x2c0
 >  [<ffffffff8d4f7e5a>] haswell_crtc_disable+0x8a/0x2e0
 >  [<ffffffff8d500e7f>] intel_atomic_commit+0xff/0x1320
 >  [<ffffffff8d4885be>] ? drm_atomic_check_only+0x21e/0x550
 >  [<ffffffff8d488927>] drm_atomic_commit+0x37/0x60
 >  [<ffffffff8d463c95>] drm_atomic_helper_set_config+0x1c5/0x430
 >  [<ffffffff8d477c95>] drm_mode_set_config_internal+0x65/0x110
 >  [<ffffffff8d4666fe>] restore_fbdev_mode+0xbe/0xe0
 >  [<ffffffff8d468565>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
 >  [<ffffffff8d4685dd>] drm_fb_helper_set_par+0x2d/0x50
 >  [<ffffffff8d517a1a>] intel_fbdev_set_par+0x1a/0x60
 >  [<ffffffff8d3aeb45>] fbcon_init+0x545/0x5d0
 >  [<ffffffff8d42d68a>] visual_init+0xca/0x130
 >  [<ffffffff8d42f495>] do_bind_con_driver+0x1c5/0x3b0
 >  [<ffffffff8d42f9b9>] do_take_over_console+0x149/0x1a0
 >  [<ffffffff8d3aa9e7>] do_fbcon_takeover+0x57/0xb0
 >  [<ffffffff8d3af5ec>] fbcon_event_notify+0x66c/0x760
 >  [<ffffffff8d09e06e>] notifier_call_chain+0x3e/0xb0
 >  [<ffffffff8d09e26d>] __blocking_notifier_call_chain+0x4d/0x70
 >  [<ffffffff8d09e2a6>] blocking_notifier_call_chain+0x16/0x20
 >  [<ffffffff8d3b4d8b>] fb_notifier_call_chain+0x1b/0x20
 >  [<ffffffff8d3b7097>] register_framebuffer+0x1e7/0x300
 >  [<ffffffff8d468852>] drm_fb_helper_initial_config+0x252/0x3e0
 >  [<ffffffff8d5184cb>] intel_fbdev_initial_config+0x1b/0x20
 >  [<ffffffff8d0a02fa>] async_run_entry_fn+0x4a/0x140
 >  [<ffffffff8d09645d>] process_one_work+0x1fd/0x670
 >  [<ffffffff8d0963cc>] ? process_one_work+0x16c/0x670
 >  [<ffffffff8d09691e>] worker_thread+0x4e/0x450
 >  [<ffffffff8d0968d0>] ? process_one_work+0x670/0x670
 >  [<ffffffff8d09ccc1>] kthread+0x101/0x120
 >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
 >  [<ffffffff8d7e764f>] ret_from_fork+0x3f/0x70
 >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
 > ---[ end trace 54cab2e0c772d5d9 ]---
 > 
 > 
 > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller (rev 06)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1230296 — Re: [Intel-gfx] [git pull] drm for 4.3

Cc'ing Maarten and Matt; I'm guessing this may be related to one of
their recent patches.

Jesse

On 09/21/2015 11:48 AM, Dave Jones wrote:
> On Mon, Sep 07, 2015 at 02:45:59PM -0400, Dave Jones wrote:
>  > On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
>  >  > 
>  >  > Hi Linus,
>  >  > 
>  >  > This is the main pull request for the drm for 4.3. Nouveau is probably the biggest
>  >  > amount of changes in here, since it missed 4.2. Highlights below, along with the usual
>  >  > bunch of fixes. There are a few minor conflicts with your tree but nothing 
>  >  > you can't handle. All stuff outside drm should have applicable acks.
>  >  > 
>  >  > Highlights:
>  >  > 
>  >  > ...
>  >  > i915:
>  >  > 	Skylake support enabled by default
>  >  > 	legacy modesetting using atomic infrastructure
>  >  > 	Skylake fixes
>  >  > 	GEN9 workarounds
>  > 
>  > Since this merge, I'm seeing this twice during boot..
> 
> And still there in -rc2.  Several other people reported this too,
> and they also got no reponse.
> 
> I'll start bisecting when I get home tonight. It shouldn't be too hard,
> as 4.2 was fine.
> 
> 	Dave
> 
>  > ------------[ cut here ]------------
>  > WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:1377 assert_planes_disabled+0xdf/0x140()
>  > plane A assertion failure, should be disabled but not
>  > CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 4.2.0-think+ #9
>  > Workqueue: events_unbound async_run_entry_fn
>  >  0000000000000561 ffff88050392b6f8 ffffffff8d7dccce ffff88050392b740
>  >  ffff88050392b730 ffffffff8d079ee2 ffff880500a60000 0000000000000000
>  >  0000000000000000 0000000000000000 ffff8805008e99c8 ffff88050392b790
>  > Call Trace:
>  >  [<ffffffff8d7dccce>] dump_stack+0x4e/0x79
>  >  [<ffffffff8d079ee2>] warn_slowpath_common+0x82/0xc0
>  >  [<ffffffff8d079f6c>] warn_slowpath_fmt+0x4c/0x50
>  >  [<ffffffff8d4ee6ff>] assert_planes_disabled+0xdf/0x140
>  >  [<ffffffff8d4f7b5b>] intel_disable_pipe+0x4b/0x2c0
>  >  [<ffffffff8d4f7e5a>] haswell_crtc_disable+0x8a/0x2e0
>  >  [<ffffffff8d500e7f>] intel_atomic_commit+0xff/0x1320
>  >  [<ffffffff8d4885be>] ? drm_atomic_check_only+0x21e/0x550
>  >  [<ffffffff8d488927>] drm_atomic_commit+0x37/0x60
>  >  [<ffffffff8d463c95>] drm_atomic_helper_set_config+0x1c5/0x430
>  >  [<ffffffff8d477c95>] drm_mode_set_config_internal+0x65/0x110
>  >  [<ffffffff8d4666fe>] restore_fbdev_mode+0xbe/0xe0
>  >  [<ffffffff8d468565>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
>  >  [<ffffffff8d4685dd>] drm_fb_helper_set_par+0x2d/0x50
>  >  [<ffffffff8d517a1a>] intel_fbdev_set_par+0x1a/0x60
>  >  [<ffffffff8d3aeb45>] fbcon_init+0x545/0x5d0
>  >  [<ffffffff8d42d68a>] visual_init+0xca/0x130
>  >  [<ffffffff8d42f495>] do_bind_con_driver+0x1c5/0x3b0
>  >  [<ffffffff8d42f9b9>] do_take_over_console+0x149/0x1a0
>  >  [<ffffffff8d3aa9e7>] do_fbcon_takeover+0x57/0xb0
>  >  [<ffffffff8d3af5ec>] fbcon_event_notify+0x66c/0x760
>  >  [<ffffffff8d09e06e>] notifier_call_chain+0x3e/0xb0
>  >  [<ffffffff8d09e26d>] __blocking_notifier_call_chain+0x4d/0x70
>  >  [<ffffffff8d09e2a6>] blocking_notifier_call_chain+0x16/0x20
>  >  [<ffffffff8d3b4d8b>] fb_notifier_call_chain+0x1b/0x20
>  >  [<ffffffff8d3b7097>] register_framebuffer+0x1e7/0x300
>  >  [<ffffffff8d468852>] drm_fb_helper_initial_config+0x252/0x3e0
>  >  [<ffffffff8d5184cb>] intel_fbdev_initial_config+0x1b/0x20
>  >  [<ffffffff8d0a02fa>] async_run_entry_fn+0x4a/0x140
>  >  [<ffffffff8d09645d>] process_one_work+0x1fd/0x670
>  >  [<ffffffff8d0963cc>] ? process_one_work+0x16c/0x670
>  >  [<ffffffff8d09691e>] worker_thread+0x4e/0x450
>  >  [<ffffffff8d0968d0>] ? process_one_work+0x670/0x670
>  >  [<ffffffff8d09ccc1>] kthread+0x101/0x120
>  >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
>  >  [<ffffffff8d7e764f>] ret_from_fork+0x3f/0x70
>  >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
>  > ---[ end trace 54cab2e0c772d5d9 ]---
>  > 
>  > 
>  > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller (rev 06)
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1230302 — [regression] [git pull] drm for 4.3

On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
> Cc'ing Maarten and Matt; I'm guessing this may be related to one of
> their recent patches.

Adding Jairo to track this regression.
-Daniel

>
> Jesse
>
> On 09/21/2015 11:48 AM, Dave Jones wrote:
> > On Mon, Sep 07, 2015 at 02:45:59PM -0400, Dave Jones wrote:
> >  > On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
> >  >  >
> >  >  > Hi Linus,
> >  >  >
> >  >  > This is the main pull request for the drm for 4.3. Nouveau is probably the biggest
> >  >  > amount of changes in here, since it missed 4.2. Highlights below, along with the usual
> >  >  > bunch of fixes. There are a few minor conflicts with your tree but nothing
> >  >  > you can't handle. All stuff outside drm should have applicable acks.
> >  >  >
> >  >  > Highlights:
> >  >  >
> >  >  > ...
> >  >  > i915:
> >  >  > Skylake support enabled by default
> >  >  > legacy modesetting using atomic infrastructure
> >  >  > Skylake fixes
> >  >  > GEN9 workarounds
> >  >
> >  > Since this merge, I'm seeing this twice during boot..
> >
> > And still there in -rc2.  Several other people reported this too,
> > and they also got no reponse.
> >
> > I'll start bisecting when I get home tonight. It shouldn't be too hard,
> > as 4.2 was fine.
> >
> > Dave
> >
> >  > ------------[ cut here ]------------
> >  > WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:1377 assert_planes_disabled+0xdf/0x140()
> >  > plane A assertion failure, should be disabled but not
> >  > CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 4.2.0-think+ #9
> >  > Workqueue: events_unbound async_run_entry_fn
> >  >  0000000000000561 ffff88050392b6f8 ffffffff8d7dccce ffff88050392b740
> >  >  ffff88050392b730 ffffffff8d079ee2 ffff880500a60000 0000000000000000
> >  >  0000000000000000 0000000000000000 ffff8805008e99c8 ffff88050392b790
> >  > Call Trace:
> >  >  [<ffffffff8d7dccce>] dump_stack+0x4e/0x79
> >  >  [<ffffffff8d079ee2>] warn_slowpath_common+0x82/0xc0
> >  >  [<ffffffff8d079f6c>] warn_slowpath_fmt+0x4c/0x50
> >  >  [<ffffffff8d4ee6ff>] assert_planes_disabled+0xdf/0x140
> >  >  [<ffffffff8d4f7b5b>] intel_disable_pipe+0x4b/0x2c0
> >  >  [<ffffffff8d4f7e5a>] haswell_crtc_disable+0x8a/0x2e0
> >  >  [<ffffffff8d500e7f>] intel_atomic_commit+0xff/0x1320
> >  >  [<ffffffff8d4885be>] ? drm_atomic_check_only+0x21e/0x550
> >  >  [<ffffffff8d488927>] drm_atomic_commit+0x37/0x60
> >  >  [<ffffffff8d463c95>] drm_atomic_helper_set_config+0x1c5/0x430
> >  >  [<ffffffff8d477c95>] drm_mode_set_config_internal+0x65/0x110
> >  >  [<ffffffff8d4666fe>] restore_fbdev_mode+0xbe/0xe0
> >  >  [<ffffffff8d468565>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
> >  >  [<ffffffff8d4685dd>] drm_fb_helper_set_par+0x2d/0x50
> >  >  [<ffffffff8d517a1a>] intel_fbdev_set_par+0x1a/0x60
> >  >  [<ffffffff8d3aeb45>] fbcon_init+0x545/0x5d0
> >  >  [<ffffffff8d42d68a>] visual_init+0xca/0x130
> >  >  [<ffffffff8d42f495>] do_bind_con_driver+0x1c5/0x3b0
> >  >  [<ffffffff8d42f9b9>] do_take_over_console+0x149/0x1a0
> >  >  [<ffffffff8d3aa9e7>] do_fbcon_takeover+0x57/0xb0
> >  >  [<ffffffff8d3af5ec>] fbcon_event_notify+0x66c/0x760
> >  >  [<ffffffff8d09e06e>] notifier_call_chain+0x3e/0xb0
> >  >  [<ffffffff8d09e26d>] __blocking_notifier_call_chain+0x4d/0x70
> >  >  [<ffffffff8d09e2a6>] blocking_notifier_call_chain+0x16/0x20
> >  >  [<ffffffff8d3b4d8b>] fb_notifier_call_chain+0x1b/0x20
> >  >  [<ffffffff8d3b7097>] register_framebuffer+0x1e7/0x300
> >  >  [<ffffffff8d468852>] drm_fb_helper_initial_config+0x252/0x3e0
> >  >  [<ffffffff8d5184cb>] intel_fbdev_initial_config+0x1b/0x20
> >  >  [<ffffffff8d0a02fa>] async_run_entry_fn+0x4a/0x140
> >  >  [<ffffffff8d09645d>] process_one_work+0x1fd/0x670
> >  >  [<ffffffff8d0963cc>] ? process_one_work+0x16c/0x670
> >  >  [<ffffffff8d09691e>] worker_thread+0x4e/0x450
> >  >  [<ffffffff8d0968d0>] ? process_one_work+0x670/0x670
> >  >  [<ffffffff8d09ccc1>] kthread+0x101/0x120
> >  >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
> >  >  [<ffffffff8d7e764f>] ret_from_fork+0x3f/0x70
> >  >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
> >  > ---[ end trace 54cab2e0c772d5d9 ]---
> >  >
> >  >
> >  > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller (rev 06)
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
>
> _______________________________________________
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1230429 — Re: [regression] [git pull] drm for 4.3

On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
> On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
> > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
> > their recent patches.

Sounds like this showed up before my recent work, but I think I might
have seen similar problems while working on atomic watermarks; the
issues I was seeing were because the initial hardware readout could
leave primary->visible set to true even when the CRTC was off.  My
series (which is still under development) contains this patch to fix
that:

        http://patchwork.freedesktop.org/patch/59564/

Does applying that help with the problems reported here?


Matt

> 
> Adding Jairo to track this regression.
> -Daniel
> 
> >
> > Jesse
> >
> > On 09/21/2015 11:48 AM, Dave Jones wrote:
> > > On Mon, Sep 07, 2015 at 02:45:59PM -0400, Dave Jones wrote:
> > >  > On Fri, Sep 04, 2015 at 11:40:53PM +0100, Dave Airlie wrote:
> > >  >  >
> > >  >  > Hi Linus,
> > >  >  >
> > >  >  > This is the main pull request for the drm for 4.3. Nouveau is probably the biggest
> > >  >  > amount of changes in here, since it missed 4.2. Highlights below, along with the usual
> > >  >  > bunch of fixes. There are a few minor conflicts with your tree but nothing
> > >  >  > you can't handle. All stuff outside drm should have applicable acks.
> > >  >  >
> > >  >  > Highlights:
> > >  >  >
> > >  >  > ...
> > >  >  > i915:
> > >  >  > Skylake support enabled by default
> > >  >  > legacy modesetting using atomic infrastructure
> > >  >  > Skylake fixes
> > >  >  > GEN9 workarounds
> > >  >
> > >  > Since this merge, I'm seeing this twice during boot..
> > >
> > > And still there in -rc2.  Several other people reported this too,
> > > and they also got no reponse.
> > >
> > > I'll start bisecting when I get home tonight. It shouldn't be too hard,
> > > as 4.2 was fine.
> > >
> > > Dave
> > >
> > >  > ------------[ cut here ]------------
> > >  > WARNING: CPU: 0 PID: 6 at drivers/gpu/drm/i915/intel_display.c:1377 assert_planes_disabled+0xdf/0x140()
> > >  > plane A assertion failure, should be disabled but not
> > >  > CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 4.2.0-think+ #9
> > >  > Workqueue: events_unbound async_run_entry_fn
> > >  >  0000000000000561 ffff88050392b6f8 ffffffff8d7dccce ffff88050392b740
> > >  >  ffff88050392b730 ffffffff8d079ee2 ffff880500a60000 0000000000000000
> > >  >  0000000000000000 0000000000000000 ffff8805008e99c8 ffff88050392b790
> > >  > Call Trace:
> > >  >  [<ffffffff8d7dccce>] dump_stack+0x4e/0x79
> > >  >  [<ffffffff8d079ee2>] warn_slowpath_common+0x82/0xc0
> > >  >  [<ffffffff8d079f6c>] warn_slowpath_fmt+0x4c/0x50
> > >  >  [<ffffffff8d4ee6ff>] assert_planes_disabled+0xdf/0x140
> > >  >  [<ffffffff8d4f7b5b>] intel_disable_pipe+0x4b/0x2c0
> > >  >  [<ffffffff8d4f7e5a>] haswell_crtc_disable+0x8a/0x2e0
> > >  >  [<ffffffff8d500e7f>] intel_atomic_commit+0xff/0x1320
> > >  >  [<ffffffff8d4885be>] ? drm_atomic_check_only+0x21e/0x550
> > >  >  [<ffffffff8d488927>] drm_atomic_commit+0x37/0x60
> > >  >  [<ffffffff8d463c95>] drm_atomic_helper_set_config+0x1c5/0x430
> > >  >  [<ffffffff8d477c95>] drm_mode_set_config_internal+0x65/0x110
> > >  >  [<ffffffff8d4666fe>] restore_fbdev_mode+0xbe/0xe0
> > >  >  [<ffffffff8d468565>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
> > >  >  [<ffffffff8d4685dd>] drm_fb_helper_set_par+0x2d/0x50
> > >  >  [<ffffffff8d517a1a>] intel_fbdev_set_par+0x1a/0x60
> > >  >  [<ffffffff8d3aeb45>] fbcon_init+0x545/0x5d0
> > >  >  [<ffffffff8d42d68a>] visual_init+0xca/0x130
> > >  >  [<ffffffff8d42f495>] do_bind_con_driver+0x1c5/0x3b0
> > >  >  [<ffffffff8d42f9b9>] do_take_over_console+0x149/0x1a0
> > >  >  [<ffffffff8d3aa9e7>] do_fbcon_takeover+0x57/0xb0
> > >  >  [<ffffffff8d3af5ec>] fbcon_event_notify+0x66c/0x760
> > >  >  [<ffffffff8d09e06e>] notifier_call_chain+0x3e/0xb0
> > >  >  [<ffffffff8d09e26d>] __blocking_notifier_call_chain+0x4d/0x70
> > >  >  [<ffffffff8d09e2a6>] blocking_notifier_call_chain+0x16/0x20
> > >  >  [<ffffffff8d3b4d8b>] fb_notifier_call_chain+0x1b/0x20
> > >  >  [<ffffffff8d3b7097>] register_framebuffer+0x1e7/0x300
> > >  >  [<ffffffff8d468852>] drm_fb_helper_initial_config+0x252/0x3e0
> > >  >  [<ffffffff8d5184cb>] intel_fbdev_initial_config+0x1b/0x20
> > >  >  [<ffffffff8d0a02fa>] async_run_entry_fn+0x4a/0x140
> > >  >  [<ffffffff8d09645d>] process_one_work+0x1fd/0x670
> > >  >  [<ffffffff8d0963cc>] ? process_one_work+0x16c/0x670
> > >  >  [<ffffffff8d09691e>] worker_thread+0x4e/0x450
> > >  >  [<ffffffff8d0968d0>] ? process_one_work+0x670/0x670
> > >  >  [<ffffffff8d09ccc1>] kthread+0x101/0x120
> > >  >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
> > >  >  [<ffffffff8d7e764f>] ret_from_fork+0x3f/0x70
> > >  >  [<ffffffff8d09cbc0>] ? kthread_create_on_node+0x250/0x250
> > >  > ---[ end trace 54cab2e0c772d5d9 ]---
> > >  >
> > >  >
> > >  > 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller (rev 06)
> > >
> > > _______________________________________________
> > > Intel-gfx mailing list
> > > Intel-gfx@lists.freedesktop.org
> > > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> > >
> >
> > _______________________________________________
> > 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

-- 
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1231092 — Re: [regression] [git pull] drm for 4.3

On Tue, Sep 22, 2015 at 09:15:58AM -0700, Matt Roper wrote:
 > On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
 > > On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
 > > > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
 > > > their recent patches.
 > 
 > Sounds like this showed up before my recent work, but I think I might
 > have seen similar problems while working on atomic watermarks; the
 > issues I was seeing were because the initial hardware readout could
 > leave primary->visible set to true even when the CRTC was off.  My
 > series (which is still under development) contains this patch to fix
 > that:
 > 
 >         http://patchwork.freedesktop.org/patch/59564/
 > 
 > Does applying that help with the problems reported here?

No difference at all for me.

	Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1231341 — Re: [regression] [git pull] drm for 4.3

SGV5LA0KDQpEYXZlIEpvbmVzIHNjaHJlZWYgb3AgZGkgMjItMDktMjAxNSBvbSAyMTo0OSBbLTA0
MDBdOg0KPiBPbiBUdWUsIFNlcCAyMiwgMjAxNSBhdCAwOToxNTo1OEFNIC0wNzAwLCBNYXR0IFJv
cGVyIHdyb3RlOg0KPiAgPiBPbiBUdWUsIFNlcCAyMiwgMjAxNSBhdCAwNToxMzo1NVBNICswMjAw
LCBEYW5pZWwgVmV0dGVyIHdyb3RlOg0KPiAgPiA+IE9uIFR1ZSwgU2VwIDIyLCAyMDE1IGF0IDA4
OjAwOjE3QU0gLTA3MDAsIEplc3NlIEJhcm5lcyB3cm90ZToNCj4gID4gPiA+IENjJ2luZyBNYWFy
dGVuIGFuZCBNYXR0OyBJJ20gZ3Vlc3NpbmcgdGhpcyBtYXkgYmUgcmVsYXRlZCB0byBvbmUgb2YN
Cj4gID4gPiA+IHRoZWlyIHJlY2VudCBwYXRjaGVzLg0KPiAgPiANCj4gID4gU291bmRzIGxpa2Ug
dGhpcyBzaG93ZWQgdXAgYmVmb3JlIG15IHJlY2VudCB3b3JrLCBidXQgSSB0aGluayBJIG1pZ2h0
DQo+ICA+IGhhdmUgc2VlbiBzaW1pbGFyIHByb2JsZW1zIHdoaWxlIHdvcmtpbmcgb24gYXRvbWlj
IHdhdGVybWFya3M7IHRoZQ0KPiAgPiBpc3N1ZXMgSSB3YXMgc2VlaW5nIHdlcmUgYmVjYXVzZSB0
aGUgaW5pdGlhbCBoYXJkd2FyZSByZWFkb3V0IGNvdWxkDQo+ICA+IGxlYXZlIHByaW1hcnktPnZp
c2libGUgc2V0IHRvIHRydWUgZXZlbiB3aGVuIHRoZSBDUlRDIHdhcyBvZmYuICBNeQ0KPiAgPiBz
ZXJpZXMgKHdoaWNoIGlzIHN0aWxsIHVuZGVyIGRldmVsb3BtZW50KSBjb250YWlucyB0aGlzIHBh
dGNoIHRvIGZpeA0KPiAgPiB0aGF0Og0KPiAgPiANCj4gID4gICAgICAgICBodHRwOi8vcGF0Y2h3
b3JrLmZyZWVkZXNrdG9wLm9yZy9wYXRjaC81OTU2NC8NCj4gID4gDQo+ICA+IERvZXMgYXBwbHlp
bmcgdGhhdCBoZWxwIHdpdGggdGhlIHByb2JsZW1zIHJlcG9ydGVkIGhlcmU/DQo+IA0KPiBObyBk
aWZmZXJlbmNlIGF0IGFsbCBmb3IgbWUuDQpMb29rcyBsaWtlIGEgKHJlb3BlbmVkKSBkdXAgb2Yg
OTE5NTI/DQoNCkNhbiB5b3UgYXBwbHkgIltQQVRDSF0gZHJtL2k5MTU6IEFkZCBwcmltYXJ5IHBs
YW5lIHRvIG1hc2sgaWYgaXQncw0KdmlzaWJsZSIsIGFuZCBnZXQgbWUgdGhlIHJlc3VsdHM/DQoN
Cn5NYWFydGVuDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KSW50ZWwgSW50ZXJuYXRpb25hbCBCLlYuClJlZ2lzdGVy
ZWQgaW4gVGhlIE5ldGhlcmxhbmRzIHVuZGVyIG51bWJlciAzNDA5ODUzNQpTdGF0dXRvcnkgc2Vh
dDogSGFhcmxlbW1lcm1lZXIKUmVnaXN0ZXJlZCBhZGRyZXNzOiBDYXByb25pbGFhbiAzNywgMTEx
OU5HIFNjaGlwaG9sLVJpamsKClRoaXMgZS1tYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgbWF5IGNv
bnRhaW4gY29uZmlkZW50aWFsIG1hdGVyaWFsIGZvcgp0aGUgc29sZSB1c2Ugb2YgdGhlIGludGVu
ZGVkIHJlY2lwaWVudChzKS4gQW55IHJldmlldyBvciBkaXN0cmlidXRpb24KYnkgb3RoZXJzIGlz
IHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZApyZWNpcGll
bnQsIHBsZWFzZSBjb250YWN0IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSBhbGwgY29waWVzLgo=

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1231845 — Re: [regression] [git pull] drm for 4.3

On Wed, Sep 23, 2015 at 11:07:56AM +0000, Lankhorst, Maarten wrote:
 > Hey,
 > 
 > Dave Jones schreef op di 22-09-2015 om 21:49 [-0400]:
 > > On Tue, Sep 22, 2015 at 09:15:58AM -0700, Matt Roper wrote:
 > >  > On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
 > >  > > On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
 > >  > > > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
 > >  > > > their recent patches.
 > >  > 
 > >  > Sounds like this showed up before my recent work, but I think I might
 > >  > have seen similar problems while working on atomic watermarks; the
 > >  > issues I was seeing were because the initial hardware readout could
 > >  > leave primary->visible set to true even when the CRTC was off.  My
 > >  > series (which is still under development) contains this patch to fix
 > >  > that:
 > >  > 
 > >  >         http://patchwork.freedesktop.org/patch/59564/
 > >  > 
 > >  > Does applying that help with the problems reported here?
 > > 
 > > No difference at all for me.
 > Looks like a (reopened) dup of 91952?
 > 
 > Can you apply "[PATCH] drm/i915: Add primary plane to mask if it's
 > visible", and get me the results?

This doesn't apply on top of Linus' current tree.
If you let me know what it's dependant on, I'll do a build with
those patches tomorrow.

	Dave
 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1232099 — Re: [regression] [git pull] drm for 4.3

On Thu, 24 Sep 2015, "davej@codemonkey.org.uk" <davej@codemonkey.org.uk> wrote:
> On Wed, Sep 23, 2015 at 11:07:56AM +0000, Lankhorst, Maarten wrote:
>  > Hey,
>  > 
>  > Dave Jones schreef op di 22-09-2015 om 21:49 [-0400]:
>  > > On Tue, Sep 22, 2015 at 09:15:58AM -0700, Matt Roper wrote:
>  > >  > On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
>  > >  > > On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
>  > >  > > > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
>  > >  > > > their recent patches.
>  > >  > 
>  > >  > Sounds like this showed up before my recent work, but I think I might
>  > >  > have seen similar problems while working on atomic watermarks; the
>  > >  > issues I was seeing were because the initial hardware readout could
>  > >  > leave primary->visible set to true even when the CRTC was off.  My
>  > >  > series (which is still under development) contains this patch to fix
>  > >  > that:
>  > >  > 
>  > >  >         http://patchwork.freedesktop.org/patch/59564/
>  > >  > 
>  > >  > Does applying that help with the problems reported here?
>  > > 
>  > > No difference at all for me.
>  > Looks like a (reopened) dup of 91952?
>  > 
>  > Can you apply "[PATCH] drm/i915: Add primary plane to mask if it's
>  > visible", and get me the results?
>
> This doesn't apply on top of Linus' current tree.
> If you let me know what it's dependant on, I'll do a build with
> those patches tomorrow.

It's now part of the drm-intel-fixes pull request [1], maybe it's
easiest to pull that in? Just four commits on top of
v4.3-rc2. Alternatively pick it up from our repo [2].

Thanks,
Jani.



[1] http://mid.gmane.org/87si646uyf.fsf@intel.com
[2] http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=721a09f7393de6c28a07516dccd654c6e995944a

>
> 	Dave
>  

-- 
Jani Nikula, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1235686 — Re: [regression] [git pull] drm for 4.3

On Thu, Sep 24, 2015 at 04:26:28PM +0300, Jani Nikula wrote:
 > On Thu, 24 Sep 2015, "davej@codemonkey.org.uk" <davej@codemonkey.org.uk> wrote:
 > > On Wed, Sep 23, 2015 at 11:07:56AM +0000, Lankhorst, Maarten wrote:
 > >  > Hey,
 > >  > 
 > >  > Dave Jones schreef op di 22-09-2015 om 21:49 [-0400]:
 > >  > > On Tue, Sep 22, 2015 at 09:15:58AM -0700, Matt Roper wrote:
 > >  > >  > On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
 > >  > >  > > On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
 > >  > >  > > > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
 > >  > >  > > > their recent patches.
 > >  > >  > 
 > >  > >  > Sounds like this showed up before my recent work, but I think I might
 > >  > >  > have seen similar problems while working on atomic watermarks; the
 > >  > >  > issues I was seeing were because the initial hardware readout could
 > >  > >  > leave primary->visible set to true even when the CRTC was off.  My
 > >  > >  > series (which is still under development) contains this patch to fix
 > >  > >  > that:
 > >  > >  > 
 > >  > >  >         http://patchwork.freedesktop.org/patch/59564/
 > >  > >  > 
 > >  > >  > Does applying that help with the problems reported here?
 > >  > > 
 > >  > > No difference at all for me.
 > >  > Looks like a (reopened) dup of 91952?
 > >  > 
 > >  > Can you apply "[PATCH] drm/i915: Add primary plane to mask if it's
 > >  > visible", and get me the results?
 > >
 > > This doesn't apply on top of Linus' current tree.
 > > If you let me know what it's dependant on, I'll do a build with
 > > those patches tomorrow.
 > 
 > It's now part of the drm-intel-fixes pull request [1], maybe it's
 > easiest to pull that in? Just four commits on top of
 > v4.3-rc2. Alternatively pick it up from our repo [2].

The warning on boot seems to be gone as of rc3, but I can now trigger this pretty easily..

WARNING: CPU: 2 PID: 28911 at drivers/gpu/drm/drm_atomic.c:889 drm_atomic_get_property+0x244/0x2d0()
CPU: 2 PID: 28911 Comm: trinity-c313 Not tainted 4.3.0-rc3-think+ #14
 0000000000000379 ffff8801a1377c88 ffffffff8e35d5ec 0000000000000000
 ffff8801a1377cc0 ffffffff8e07a862 ffff880500b392b8 ffff880500a13008
 ffff880500b39290 ffff8804fe3806d8 ffff88003fa45668 ffff8801a1377cd0
Call Trace:
 [<ffffffff8e35d5ec>] dump_stack+0x4e/0x82
 [<ffffffff8e07a862>] warn_slowpath_common+0x82/0xc0
 [<ffffffff8e07a95a>] warn_slowpath_null+0x1a/0x20
 [<ffffffff8e48efc4>] drm_atomic_get_property+0x244/0x2d0
 [<ffffffff8e47c7fc>] drm_object_property_get_value+0x6c/0x70
 [<ffffffff8e47a41f>] dpms_show+0x2f/0x70
 [<ffffffff8e54ce30>] dev_attr_show+0x20/0x50
 [<ffffffff8e27ae91>] ? sysfs_file_ops+0x41/0x60
 [<ffffffff8e27b1a7>] sysfs_kf_seq_show+0xb7/0x110
 [<ffffffff8e2799a6>] kernfs_seq_show+0x26/0x30
 [<ffffffff8e21bba6>] seq_read+0xe6/0x430
 [<ffffffff8e27a3f7>] kernfs_fop_read+0x127/0x170
 [<ffffffff8e7e987b>] ? mutex_lock_nested+0x26b/0x3f0
 [<ffffffff8e1f3af8>] __vfs_read+0x28/0xe0
 [<ffffffff8e7e9897>] ? mutex_lock_nested+0x287/0x3f0
 [<ffffffff8e214c09>] ? __fdget_pos+0x49/0x50
 [<ffffffff8e214c09>] ? __fdget_pos+0x49/0x50
 [<ffffffff8e1f43c6>] vfs_read+0x86/0x130
 [<ffffffff8e1f50a9>] SyS_read+0x49/0xb0
 [<ffffffff8e7eded7>] entry_SYSCALL_64_fastpath+0x12/0x6f
---[ end trace e053063c697a1355 ]---

 887         case DRM_MODE_OBJECT_CONNECTOR: {
 888                 struct drm_connector *connector = obj_to_connector(obj);
 889                 WARN_ON(!drm_modeset_is_locked(&dev->mode_config.connection_mutex));
 890                 ret = drm_atomic_connector_get_property(connector,
 891                                 connector->state, property, val);
 892                 break;
 893         }

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1235816 — Re: [regression] [git pull] drm for 4.3

On Tue, Sep 29, 2015 at 09:07:22PM -0400, davej@codemonkey.org.uk wrote:
> On Thu, Sep 24, 2015 at 04:26:28PM +0300, Jani Nikula wrote:
>  > On Thu, 24 Sep 2015, "davej@codemonkey.org.uk" <davej@codemonkey.org.uk> wrote:
>  > > On Wed, Sep 23, 2015 at 11:07:56AM +0000, Lankhorst, Maarten wrote:
>  > >  > Hey,
>  > >  > 
>  > >  > Dave Jones schreef op di 22-09-2015 om 21:49 [-0400]:
>  > >  > > On Tue, Sep 22, 2015 at 09:15:58AM -0700, Matt Roper wrote:
>  > >  > >  > On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
>  > >  > >  > > On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
>  > >  > >  > > > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
>  > >  > >  > > > their recent patches.
>  > >  > >  > 
>  > >  > >  > Sounds like this showed up before my recent work, but I think I might
>  > >  > >  > have seen similar problems while working on atomic watermarks; the
>  > >  > >  > issues I was seeing were because the initial hardware readout could
>  > >  > >  > leave primary->visible set to true even when the CRTC was off.  My
>  > >  > >  > series (which is still under development) contains this patch to fix
>  > >  > >  > that:
>  > >  > >  > 
>  > >  > >  >         http://patchwork.freedesktop.org/patch/59564/
>  > >  > >  > 
>  > >  > >  > Does applying that help with the problems reported here?
>  > >  > > 
>  > >  > > No difference at all for me.
>  > >  > Looks like a (reopened) dup of 91952?
>  > >  > 
>  > >  > Can you apply "[PATCH] drm/i915: Add primary plane to mask if it's
>  > >  > visible", and get me the results?
>  > >
>  > > This doesn't apply on top of Linus' current tree.
>  > > If you let me know what it's dependant on, I'll do a build with
>  > > those patches tomorrow.
>  > 
>  > It's now part of the drm-intel-fixes pull request [1], maybe it's
>  > easiest to pull that in? Just four commits on top of
>  > v4.3-rc2. Alternatively pick it up from our repo [2].
> 
> The warning on boot seems to be gone as of rc3, but I can now trigger this pretty easily..

http://patchwork.freedesktop.org/patch/60618/

Cheers, Daniel

> 
> WARNING: CPU: 2 PID: 28911 at drivers/gpu/drm/drm_atomic.c:889 drm_atomic_get_property+0x244/0x2d0()
> CPU: 2 PID: 28911 Comm: trinity-c313 Not tainted 4.3.0-rc3-think+ #14
>  0000000000000379 ffff8801a1377c88 ffffffff8e35d5ec 0000000000000000
>  ffff8801a1377cc0 ffffffff8e07a862 ffff880500b392b8 ffff880500a13008
>  ffff880500b39290 ffff8804fe3806d8 ffff88003fa45668 ffff8801a1377cd0
> Call Trace:
>  [<ffffffff8e35d5ec>] dump_stack+0x4e/0x82
>  [<ffffffff8e07a862>] warn_slowpath_common+0x82/0xc0
>  [<ffffffff8e07a95a>] warn_slowpath_null+0x1a/0x20
>  [<ffffffff8e48efc4>] drm_atomic_get_property+0x244/0x2d0
>  [<ffffffff8e47c7fc>] drm_object_property_get_value+0x6c/0x70
>  [<ffffffff8e47a41f>] dpms_show+0x2f/0x70
>  [<ffffffff8e54ce30>] dev_attr_show+0x20/0x50
>  [<ffffffff8e27ae91>] ? sysfs_file_ops+0x41/0x60
>  [<ffffffff8e27b1a7>] sysfs_kf_seq_show+0xb7/0x110
>  [<ffffffff8e2799a6>] kernfs_seq_show+0x26/0x30
>  [<ffffffff8e21bba6>] seq_read+0xe6/0x430
>  [<ffffffff8e27a3f7>] kernfs_fop_read+0x127/0x170
>  [<ffffffff8e7e987b>] ? mutex_lock_nested+0x26b/0x3f0
>  [<ffffffff8e1f3af8>] __vfs_read+0x28/0xe0
>  [<ffffffff8e7e9897>] ? mutex_lock_nested+0x287/0x3f0
>  [<ffffffff8e214c09>] ? __fdget_pos+0x49/0x50
>  [<ffffffff8e214c09>] ? __fdget_pos+0x49/0x50
>  [<ffffffff8e1f43c6>] vfs_read+0x86/0x130
>  [<ffffffff8e1f50a9>] SyS_read+0x49/0xb0
>  [<ffffffff8e7eded7>] entry_SYSCALL_64_fastpath+0x12/0x6f
> ---[ end trace e053063c697a1355 ]---
> 
>  887         case DRM_MODE_OBJECT_CONNECTOR: {
>  888                 struct drm_connector *connector = obj_to_connector(obj);
>  889                 WARN_ON(!drm_modeset_is_locked(&dev->mode_config.connection_mutex));
>  890                 ret = drm_atomic_connector_get_property(connector,
>  891                                 connector->state, property, val);
>  892                 break;
>  893         }
> 
> _______________________________________________
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1234754 — [Intel-gfx] [regression] boot to the blackscreen with the kernel 4.3

hi,
     when use the latest 4.3-rc3kernel,
the fedora rawhide will boot to the blackscreen,and never got the gdm 
login screen.

the fellowing is the boot log about drm.
[drm] Initialized drm 1.1.0 20060810
[drm] Memory usable by graphics device = 2048M
[drm] Replacing VGA console driver
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
[drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't 
calculate constants, dotclock = 0!
[drm] Initialized i915 1.6.0 20150731 for 0000:00:02.0 on minor 0


lspci
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller 
(rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)
00:03.0 Communication controller: Intel Corporation 4 Series Chipset 
HECI Controller (rev 03)
00:03.2 IDE interface: Intel Corporation 4 Series Chipset PT IDER 
Controller (rev 03)
00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT 
Controller (rev 03)
00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network 
Connection (rev 02)
00:1a.0 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB 
UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB 
UHCI Controller #5 (rev 02)
00:1a.2 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB 
UHCI Controller #6 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 
EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801JD/DO (ICH10 Family) HD 
Audio Controller (rev 02)
00:1d.0 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB 
UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB 
UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB 
UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801JD/DO (ICH10 Family) USB2 
EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2)
00:1f.0 ISA bridge: Intel Corporation 82801JDO (ICH10DO) LPC Interface 
Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801JD/DO (ICH10 Family) 
4-port SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801JD/DO (ICH10 Family) SMBus 
Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801JD/DO (ICH10 Family) 
2-port SATA IDE Controller (rev 02)

thanks
chunshan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web