All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Dave Jones <davej@codemonkey.org.uk>,
	Dave Airlie <airlied@linux.ie>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Lankhorst, Maarten" <maarten.lankhorst@intel.com>,
	Jairo Miramontes <jairo.daniel.miramontes.caton@intel.com>
Subject: Re: [regression] [git pull] drm for 4.3
Date: Tue, 22 Sep 2015 09:15:58 -0700	[thread overview]
Message-ID: <20150922161558.GB24128@intel.com> (raw)
In-Reply-To: <20150922151355.GX3383@phenom.ffwll.local>

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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Matt Roper <matthew.d.roper@intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Dave Jones <davej@codemonkey.org.uk>,
	Dave Airlie <airlied@linux.ie>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Lankhorst, Maarten" <maarten.lankhorst@intel.com>,
	Jairo Miramontes <jairo.daniel.miramontes.caton@intel.com>
Subject: Re: [regression] [git pull] drm for 4.3
Date: Tue, 22 Sep 2015 09:15:58 -0700	[thread overview]
Message-ID: <20150922161558.GB24128@intel.com> (raw)
In-Reply-To: <20150922151355.GX3383@phenom.ffwll.local>

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

  reply	other threads:[~2015-09-22 16:15 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 22:40 [git pull] drm for 4.3 Dave Airlie
2015-09-04 22:40 ` Dave Airlie
2015-09-07 18:45 ` Dave Jones
2015-09-07 18:45   ` Dave Jones
2015-09-21 18:48   ` Dave Jones
2015-09-21 18:48     ` Dave Jones
2015-09-22 15:00     ` Jesse Barnes
2015-09-22 15:00       ` [Intel-gfx] " Jesse Barnes
2015-09-22 15:13       ` [regression] " Daniel Vetter
2015-09-22 15:13         ` Daniel Vetter
2015-09-22 16:15         ` Matt Roper [this message]
2015-09-22 16:15           ` Matt Roper
2015-09-23  1:49           ` Dave Jones
2015-09-23  1:49             ` Dave Jones
2015-09-23 11:07             ` Lankhorst, Maarten
2015-09-23 11:07               ` Lankhorst, Maarten
2015-09-24  3:51               ` davej
2015-09-24  3:51                 ` davej
2015-09-24 13:26                 ` Jani Nikula
2015-09-24 13:26                   ` Jani Nikula
2015-09-30  1:07                   ` davej
2015-09-30  1:07                     ` davej
2015-09-30  6:56                     ` Daniel Vetter
2015-09-30  6:56                       ` Daniel Vetter
2015-10-19 20:19                       ` davej
2015-10-19 20:19                         ` davej
2015-10-19 21:54                         ` Daniel Vetter
2015-10-19 21:54                           ` [Intel-gfx] " Daniel Vetter
2015-10-20  5:33                           ` Dave Airlie
2015-10-20  5:33                             ` [Intel-gfx] " Dave Airlie
2015-10-20 14:42                             ` davej
2015-10-20 14:42                               ` [Intel-gfx] " davej
2015-09-29  6:43                 ` [regression] boot to the blackscreen with the kernel 4.3 zhuhuachun
2015-09-29  6:43                   ` [Intel-gfx] " zhuhuachun
2015-09-08  2:03 ` [git pull] drm for 4.3 Stephen Rothwell
2015-09-08  2:03   ` Stephen Rothwell
2015-09-08  3:01   ` Dave Airlie
2015-09-08  3:01     ` Dave Airlie
2015-09-08  4:04     ` Stephen Rothwell
2015-09-08  4:04       ` Stephen Rothwell
2015-09-08  4:56       ` Dave Airlie
2015-09-08  4:56         ` Dave Airlie
2015-09-08 18:19         ` Linus Torvalds
2015-09-08 18:19           ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150922161558.GB24128@intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=davej@codemonkey.org.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jairo.daniel.miramontes.caton@intel.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@intel.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.