Re: [git pull] drm for 4.3

2015-09-21 Thread Dave Jones 
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
 >  0561 88050392b6f8 8d7dccce 88050392b740
 >  88050392b730 8d079ee2 880500a6 
 >    8805008e99c8 88050392b790
 > Call Trace:
 >  [] dump_stack+0x4e/0x79
 >  [] warn_slowpath_common+0x82/0xc0
 >  [] warn_slowpath_fmt+0x4c/0x50
 >  [] assert_planes_disabled+0xdf/0x140
 >  [] intel_disable_pipe+0x4b/0x2c0
 >  [] haswell_crtc_disable+0x8a/0x2e0
 >  [] intel_atomic_commit+0xff/0x1320
 >  [] ? drm_atomic_check_only+0x21e/0x550
 >  [] drm_atomic_commit+0x37/0x60
 >  [] drm_atomic_helper_set_config+0x1c5/0x430
 >  [] drm_mode_set_config_internal+0x65/0x110
 >  [] restore_fbdev_mode+0xbe/0xe0
 >  [] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
 >  [] drm_fb_helper_set_par+0x2d/0x50
 >  [] intel_fbdev_set_par+0x1a/0x60
 >  [] fbcon_init+0x545/0x5d0
 >  [] visual_init+0xca/0x130
 >  [] do_bind_con_driver+0x1c5/0x3b0
 >  [] do_take_over_console+0x149/0x1a0
 >  [] do_fbcon_takeover+0x57/0xb0
 >  [] fbcon_event_notify+0x66c/0x760
 >  [] notifier_call_chain+0x3e/0xb0
 >  [] __blocking_notifier_call_chain+0x4d/0x70
 >  [] blocking_notifier_call_chain+0x16/0x20
 >  [] fb_notifier_call_chain+0x1b/0x20
 >  [] register_framebuffer+0x1e7/0x300
 >  [] drm_fb_helper_initial_config+0x252/0x3e0
 >  [] intel_fbdev_initial_config+0x1b/0x20
 >  [] async_run_entry_fn+0x4a/0x140
 >  [] process_one_work+0x1fd/0x670
 >  [] ? process_one_work+0x16c/0x670
 >  [] worker_thread+0x4e/0x450
 >  [] ? process_one_work+0x670/0x670
 >  [] kthread+0x101/0x120
 >  [] ? kthread_create_on_node+0x250/0x250
 >  [] ret_from_fork+0x3f/0x70
 >  [] ? 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 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: [git pull] drm for 4.3

2015-09-21 Thread Dave Jones 
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
 >  0561 88050392b6f8 8d7dccce 88050392b740
 >  88050392b730 8d079ee2 880500a6 
 >    8805008e99c8 88050392b790
 > Call Trace:
 >  [] dump_stack+0x4e/0x79
 >  [] warn_slowpath_common+0x82/0xc0
 >  [] warn_slowpath_fmt+0x4c/0x50
 >  [] assert_planes_disabled+0xdf/0x140
 >  [] intel_disable_pipe+0x4b/0x2c0
 >  [] haswell_crtc_disable+0x8a/0x2e0
 >  [] intel_atomic_commit+0xff/0x1320
 >  [] ? drm_atomic_check_only+0x21e/0x550
 >  [] drm_atomic_commit+0x37/0x60
 >  [] drm_atomic_helper_set_config+0x1c5/0x430
 >  [] drm_mode_set_config_internal+0x65/0x110
 >  [] restore_fbdev_mode+0xbe/0xe0
 >  [] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
 >  [] drm_fb_helper_set_par+0x2d/0x50
 >  [] intel_fbdev_set_par+0x1a/0x60
 >  [] fbcon_init+0x545/0x5d0
 >  [] visual_init+0xca/0x130
 >  [] do_bind_con_driver+0x1c5/0x3b0
 >  [] do_take_over_console+0x149/0x1a0
 >  [] do_fbcon_takeover+0x57/0xb0
 >  [] fbcon_event_notify+0x66c/0x760
 >  [] notifier_call_chain+0x3e/0xb0
 >  [] __blocking_notifier_call_chain+0x4d/0x70
 >  [] blocking_notifier_call_chain+0x16/0x20
 >  [] fb_notifier_call_chain+0x1b/0x20
 >  [] register_framebuffer+0x1e7/0x300
 >  [] drm_fb_helper_initial_config+0x252/0x3e0
 >  [] intel_fbdev_initial_config+0x1b/0x20
 >  [] async_run_entry_fn+0x4a/0x140
 >  [] process_one_work+0x1fd/0x670
 >  [] ? process_one_work+0x16c/0x670
 >  [] worker_thread+0x4e/0x450
 >  [] ? process_one_work+0x670/0x670
 >  [] kthread+0x101/0x120
 >  [] ? kthread_create_on_node+0x250/0x250
 >  [] ret_from_fork+0x3f/0x70
 >  [] ? 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 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: [git pull] drm for 4.3

2015-09-08 Thread Linus Torvalds 
On Mon, Sep 7, 2015 at 9:56 PM, Dave Airlie  wrote:
>
> i.e. 59 commits in a 5000 commit tree is likely not that bad, 59
> commits in a 20 commit tree would be bad.

I think it's about size of the commits. If it's 59 clean oneliner
fixes, I don't think it's a big deal. If it's 59 patches that add new
functionality, that's a different issue. The size of the base tree is
almost entirely irrelevant in that situation. Fixes are ok, new
features are not.

  Linus
--
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: [git pull] drm for 4.3

2015-09-08 Thread Linus Torvalds 
On Mon, Sep 7, 2015 at 9:56 PM, Dave Airlie  wrote:
>
> i.e. 59 commits in a 5000 commit tree is likely not that bad, 59
> commits in a 20 commit tree would be bad.

I think it's about size of the commits. If it's 59 clean oneliner
fixes, I don't think it's a big deal. If it's 59 patches that add new
functionality, that's a different issue. The size of the base tree is
almost entirely irrelevant in that situation. Fixes are ok, new
features are not.

  Linus
--
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: [git pull] drm for 4.3

2015-09-07 Thread Dave Airlie 
On 8 September 2015 at 14:04, Stephen Rothwell  wrote:
> Hi Dave,
>
> On Tue, 8 Sep 2015 13:01:21 +1000 Dave Airlie  wrote:
>>
>> Is this to be a regular thing? because I know I'd prefer to merge
>> fixes than wait for -rc1 to be an accurate copy of linux-next.
>
> It happens when I can (almost) keep up with Linus' merge rate (often I
> can't).  It is not an issue and I agree that fixes should just be done
> as/when needed.  That is why I say "not judging, just noting" - I
> generally don't have the time to figure out if each and every unseen
> commit is a fix or new feature and/or if it has some possibility of
> interacting with some other tree in a way that a few days in linux-next
> may have flushed out.
>
> So, if you are happy with what you are doing (and you don't irritate
> Linus), then I am happy (as long as you don't cause unnecessary extra
> conflicts in linux-next :-)).
>

Maybe you could heuristic it by ratio new commits or new lines vs the
total size of the -next tree.

i.e. 59 commits in a 5000 commit tree is likely not that bad, 59
commits in a 20 commit tree would be bad.

Though not sure how you'd tune it!

Dave.
--
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: [git pull] drm for 4.3

2015-09-07 Thread Stephen Rothwell 
Hi Dave,

On Tue, 8 Sep 2015 13:01:21 +1000 Dave Airlie  wrote:
>
> Is this to be a regular thing? because I know I'd prefer to merge
> fixes than wait for -rc1 to be an accurate copy of linux-next.

It happens when I can (almost) keep up with Linus' merge rate (often I
can't).  It is not an issue and I agree that fixes should just be done
as/when needed.  That is why I say "not judging, just noting" - I
generally don't have the time to figure out if each and every unseen
commit is a fix or new feature and/or if it has some possibility of
interacting with some other tree in a way that a few days in linux-next
may have flushed out.

So, if you are happy with what you are doing (and you don't irritate
Linus), then I am happy (as long as you don't cause unnecessary extra
conflicts in linux-next :-)).

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
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: [git pull] drm for 4.3

2015-09-07 Thread Dave Airlie 
On 8 September 2015 at 12:03, Stephen Rothwell  wrote:
> Hi Linus,
>
> On Fri, 4 Sep 2015 23:40:53 +0100 (IST) Dave Airlie  wrote:
>>
>> 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.
>>
>> The following changes since commit c13dcf9f2d6f5f06ef1bf79ec456df614c5e058b:
>>
>>   Linux 4.2-rc8 (2015-08-23 20:52:59 -0700)
>>
>> are available in the git repository at:
>>
>>   git://people.freedesktop.org/~airlied/linux drm-next
>>
>> for you to fetch changes up to 73bf1b7be7aab60d7c651402441dd0b0b4991098:
>>
>>   Merge branch 'drm-next-4.3' of git://people.freedesktop.org/~agd5f/linux 
>> into drm-next (2015-09-05 07:46:09 +1000)
>
> This contains 59 commits added since Sept 1 and 56 of those are only
> appearing in today's linux-next.  Not judging, just noting.

Is this to be a regular thing? because I know I'd prefer to merge
fixes than wait for -rc1 to be an accurate copy of linux-next.

Dave.
--
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: [git pull] drm for 4.3

2015-09-07 Thread Stephen Rothwell 
Hi Linus,

On Fri, 4 Sep 2015 23:40:53 +0100 (IST) Dave Airlie  wrote:
>
> 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.
> 
> The following changes since commit c13dcf9f2d6f5f06ef1bf79ec456df614c5e058b:
> 
>   Linux 4.2-rc8 (2015-08-23 20:52:59 -0700)
> 
> are available in the git repository at:
> 
>   git://people.freedesktop.org/~airlied/linux drm-next
> 
> for you to fetch changes up to 73bf1b7be7aab60d7c651402441dd0b0b4991098:
> 
>   Merge branch 'drm-next-4.3' of git://people.freedesktop.org/~agd5f/linux 
> into drm-next (2015-09-05 07:46:09 +1000)

This contains 59 commits added since Sept 1 and 56 of those are only
appearing in today's linux-next.  Not judging, just noting.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
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: [git pull] drm for 4.3

2015-09-07 Thread Dave Jones 
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
 0561 88050392b6f8 8d7dccce 88050392b740
 88050392b730 8d079ee2 880500a6 
   8805008e99c8 88050392b790
Call Trace:
 [] dump_stack+0x4e/0x79
 [] warn_slowpath_common+0x82/0xc0
 [] warn_slowpath_fmt+0x4c/0x50
 [] assert_planes_disabled+0xdf/0x140
 [] intel_disable_pipe+0x4b/0x2c0
 [] haswell_crtc_disable+0x8a/0x2e0
 [] intel_atomic_commit+0xff/0x1320
 [] ? drm_atomic_check_only+0x21e/0x550
 [] drm_atomic_commit+0x37/0x60
 [] drm_atomic_helper_set_config+0x1c5/0x430
 [] drm_mode_set_config_internal+0x65/0x110
 [] restore_fbdev_mode+0xbe/0xe0
 [] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
 [] drm_fb_helper_set_par+0x2d/0x50
 [] intel_fbdev_set_par+0x1a/0x60
 [] fbcon_init+0x545/0x5d0
 [] visual_init+0xca/0x130
 [] do_bind_con_driver+0x1c5/0x3b0
 [] do_take_over_console+0x149/0x1a0
 [] do_fbcon_takeover+0x57/0xb0
 [] fbcon_event_notify+0x66c/0x760
 [] notifier_call_chain+0x3e/0xb0
 [] __blocking_notifier_call_chain+0x4d/0x70
 [] blocking_notifier_call_chain+0x16/0x20
 [] fb_notifier_call_chain+0x1b/0x20
 [] register_framebuffer+0x1e7/0x300
 [] drm_fb_helper_initial_config+0x252/0x3e0
 [] intel_fbdev_initial_config+0x1b/0x20
 [] async_run_entry_fn+0x4a/0x140
 [] process_one_work+0x1fd/0x670
 [] ? process_one_work+0x16c/0x670
 [] worker_thread+0x4e/0x450
 [] ? process_one_work+0x670/0x670
 [] kthread+0x101/0x120
 [] ? kthread_create_on_node+0x250/0x250
 [] ret_from_fork+0x3f/0x70
 [] ? 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 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: [git pull] drm for 4.3

2015-09-07 Thread Dave Airlie 
On 8 September 2015 at 14:04, Stephen Rothwell  wrote:
> Hi Dave,
>
> On Tue, 8 Sep 2015 13:01:21 +1000 Dave Airlie  wrote:
>>
>> Is this to be a regular thing? because I know I'd prefer to merge
>> fixes than wait for -rc1 to be an accurate copy of linux-next.
>
> It happens when I can (almost) keep up with Linus' merge rate (often I
> can't).  It is not an issue and I agree that fixes should just be done
> as/when needed.  That is why I say "not judging, just noting" - I
> generally don't have the time to figure out if each and every unseen
> commit is a fix or new feature and/or if it has some possibility of
> interacting with some other tree in a way that a few days in linux-next
> may have flushed out.
>
> So, if you are happy with what you are doing (and you don't irritate
> Linus), then I am happy (as long as you don't cause unnecessary extra
> conflicts in linux-next :-)).
>

Maybe you could heuristic it by ratio new commits or new lines vs the
total size of the -next tree.

i.e. 59 commits in a 5000 commit tree is likely not that bad, 59
commits in a 20 commit tree would be bad.

Though not sure how you'd tune it!

Dave.
--
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: [git pull] drm for 4.3

2015-09-07 Thread Stephen Rothwell 
Hi Dave,

On Tue, 8 Sep 2015 13:01:21 +1000 Dave Airlie  wrote:
>
> Is this to be a regular thing? because I know I'd prefer to merge
> fixes than wait for -rc1 to be an accurate copy of linux-next.

It happens when I can (almost) keep up with Linus' merge rate (often I
can't).  It is not an issue and I agree that fixes should just be done
as/when needed.  That is why I say "not judging, just noting" - I
generally don't have the time to figure out if each and every unseen
commit is a fix or new feature and/or if it has some possibility of
interacting with some other tree in a way that a few days in linux-next
may have flushed out.

So, if you are happy with what you are doing (and you don't irritate
Linus), then I am happy (as long as you don't cause unnecessary extra
conflicts in linux-next :-)).

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
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: [git pull] drm for 4.3

2015-09-07 Thread Stephen Rothwell 
Hi Linus,

On Fri, 4 Sep 2015 23:40:53 +0100 (IST) Dave Airlie  wrote:
>
> 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.
> 
> The following changes since commit c13dcf9f2d6f5f06ef1bf79ec456df614c5e058b:
> 
>   Linux 4.2-rc8 (2015-08-23 20:52:59 -0700)
> 
> are available in the git repository at:
> 
>   git://people.freedesktop.org/~airlied/linux drm-next
> 
> for you to fetch changes up to 73bf1b7be7aab60d7c651402441dd0b0b4991098:
> 
>   Merge branch 'drm-next-4.3' of git://people.freedesktop.org/~agd5f/linux 
> into drm-next (2015-09-05 07:46:09 +1000)

This contains 59 commits added since Sept 1 and 56 of those are only
appearing in today's linux-next.  Not judging, just noting.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
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: [git pull] drm for 4.3

2015-09-07 Thread Dave Airlie 
On 8 September 2015 at 12:03, Stephen Rothwell  wrote:
> Hi Linus,
>
> On Fri, 4 Sep 2015 23:40:53 +0100 (IST) Dave Airlie  wrote:
>>
>> 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.
>>
>> The following changes since commit c13dcf9f2d6f5f06ef1bf79ec456df614c5e058b:
>>
>>   Linux 4.2-rc8 (2015-08-23 20:52:59 -0700)
>>
>> are available in the git repository at:
>>
>>   git://people.freedesktop.org/~airlied/linux drm-next
>>
>> for you to fetch changes up to 73bf1b7be7aab60d7c651402441dd0b0b4991098:
>>
>>   Merge branch 'drm-next-4.3' of git://people.freedesktop.org/~agd5f/linux 
>> into drm-next (2015-09-05 07:46:09 +1000)
>
> This contains 59 commits added since Sept 1 and 56 of those are only
> appearing in today's linux-next.  Not judging, just noting.

Is this to be a regular thing? because I know I'd prefer to merge
fixes than wait for -rc1 to be an accurate copy of linux-next.

Dave.
--
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: [git pull] drm for 4.3

2015-09-07 Thread Dave Jones 
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
 0561 88050392b6f8 8d7dccce 88050392b740
 88050392b730 8d079ee2 880500a6 
   8805008e99c8 88050392b790
Call Trace:
 [] dump_stack+0x4e/0x79
 [] warn_slowpath_common+0x82/0xc0
 [] warn_slowpath_fmt+0x4c/0x50
 [] assert_planes_disabled+0xdf/0x140
 [] intel_disable_pipe+0x4b/0x2c0
 [] haswell_crtc_disable+0x8a/0x2e0
 [] intel_atomic_commit+0xff/0x1320
 [] ? drm_atomic_check_only+0x21e/0x550
 [] drm_atomic_commit+0x37/0x60
 [] drm_atomic_helper_set_config+0x1c5/0x430
 [] drm_mode_set_config_internal+0x65/0x110
 [] restore_fbdev_mode+0xbe/0xe0
 [] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70
 [] drm_fb_helper_set_par+0x2d/0x50
 [] intel_fbdev_set_par+0x1a/0x60
 [] fbcon_init+0x545/0x5d0
 [] visual_init+0xca/0x130
 [] do_bind_con_driver+0x1c5/0x3b0
 [] do_take_over_console+0x149/0x1a0
 [] do_fbcon_takeover+0x57/0xb0
 [] fbcon_event_notify+0x66c/0x760
 [] notifier_call_chain+0x3e/0xb0
 [] __blocking_notifier_call_chain+0x4d/0x70
 [] blocking_notifier_call_chain+0x16/0x20
 [] fb_notifier_call_chain+0x1b/0x20
 [] register_framebuffer+0x1e7/0x300
 [] drm_fb_helper_initial_config+0x252/0x3e0
 [] intel_fbdev_initial_config+0x1b/0x20
 [] async_run_entry_fn+0x4a/0x140
 [] process_one_work+0x1fd/0x670
 [] ? process_one_work+0x16c/0x670
 [] worker_thread+0x4e/0x450
 [] ? process_one_work+0x670/0x670
 [] kthread+0x101/0x120
 [] ? kthread_create_on_node+0x250/0x250
 [] ret_from_fork+0x3f/0x70
 [] ? 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 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/