Bug 92083 - [regression] [git pull] drm for 4.3
Summary: [regression] [git pull] drm for 4.3
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-23 03:31 UTC by Jairo Miramontes
Modified: 2017-01-10 12:26 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: display/atomic


Attachments

Description Jairo Miramontes 2015-09-23 03:31:34 UTC
>
> 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
Comment 1 Jairo Miramontes 2015-09-23 03:43:01 UTC
Bug created for tracking purposes, this bug was reported through mail

Regards
Comment 2 Daniel Vetter 2015-09-23 09:17:00 UTC
(In reply to Jairo Miramontes from comment #1)
> Bug created for tracking purposes, this bug was reported through mail
> 
> Regards

Please also add a link to the intel-gfx archive here so that people can follow the m-l discussion. Even better would be a Msg-Id based url from e.g. http://mid.gmane.org/1440671138-17174-1-git-send-email-jani.nikula@intel.com

You can find the message id in the raw headers of the mail.

Please also update the BKMs in the wiki with this.
Comment 3 Daniel Vetter 2015-09-23 13:04:42 UTC
Also please follow up on the m-l with a link to this bug so that maintainers/bug reports are aware of this. Again please add that to bkms.
Comment 4 Jani Nikula 2016-04-22 14:21:40 UTC
It doesn't work to file bugs on behalf of people who don't follow up here, when we can't reproduce the issue ourselves. Closing.
Comment 5 Jari Tahvanainen 2017-01-10 12:26:51 UTC
Closing resolved+invalid after 8 months of silence.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.