From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933402AbbCPQlz (ORCPT ); Mon, 16 Mar 2015 12:41:55 -0400 Received: from mail-wi0-f182.google.com ([209.85.212.182]:38875 "EHLO mail-wi0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933318AbbCPQlx (ORCPT ); Mon, 16 Mar 2015 12:41:53 -0400 Date: Mon, 16 Mar 2015 17:43:33 +0100 From: Daniel Vetter To: Steven Rostedt Cc: Andrey Skvortsov , Chris Wilson , Daniel Vetter , Jani Nikula , David Airlie , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Sitsofe Wheeler Subject: Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object Message-ID: <20150316164333.GJ21993@phenom.ffwll.local> Mail-Followup-To: Steven Rostedt , Andrey Skvortsov , Chris Wilson , Daniel Vetter , Jani Nikula , David Airlie , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Sitsofe Wheeler References: <20150203191507.GA2374@crion86> <20150203202152.GD5784@nuc-i3427.alporthouse.com> <20150204182627.GA2272@crion86> <20150204184217.GG10991@nuc-i3427.alporthouse.com> <20150223201239.GC3871@crion86> <20150305142728.GC3042@home.goodmis.org> <20150316114503.21846d5e@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150316114503.21846d5e@gandalf.local.home> X-Operating-System: Linux phenom 4.0.0-rc3+ User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 16, 2015 at 11:45:03AM -0400, Steven Rostedt wrote: > > Any movement on this? I still get this warning on 4.0-rc4. Sorry for not looking into this, I've thought we've addressed this already and the fix is simply still in-flight to 4.0-rc. Seems it's not :( Is linux-next also affected or is this just a case of i915 maintainers having failed to push the right patch to -fixes? I'll try to figure out what fell apart here meanwhile. To help out, can you please boot with drm.debug=0xe and grab the full dmesg for booting? Looks like it falls over in the initial fbcon modeset, which is indeed strange ... Thanks, Daniel > > -- Steve > > > On Thu, 5 Mar 2015 09:27:28 -0500 > Steven Rostedt wrote: > > > On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: > > > > > > This warning is moved from linux-next to v4.0-rc1 now. After system boot is just a black screen. > > > I ssh'ed into the machine and saved the log. I attached updated dmesg.log with drm.debug=6. Hopefully it helps. > > > If you need any other debug information, traces, core dump or something else. Feel free to ask. > > > > > > > I'm hitting this exact same warning on one of my test boxes. > > > > [drm] Initialized i915 1.6.0 20150130 for 0000:00:02.0 on minor 0 > > ------------[ cut here ]------------ > > WARNING: CPU: 7 PID: 116 at /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x2de/0x300 [i915]() > > WARN_ON(obj->frontbuffer_bits) > > Modules linked in: i915 i2c_algo_bit e1000e drm_kms_helper ptp crc32c_intel drm pps_core i2c_core video sunrpc > > CPU: 7 PID: 116 Comm: kworker/u16:5 Not tainted 4.0.0-rc1-test #270 > > Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v02.05 05/07/2012 > > Workqueue: events_unbound async_run_entry_fn > > 00000000000011ad ffff88001fa837e8 ffffffff816cc3cc 000000000000d4d4 > > ffff88001fa83838 ffff88001fa83828 ffffffff8107b977 ffff8800d4fd0000 > > ffff88001f2b5800 ffff8800d4f40040 ffff8800d4f40000 ffff8800d4f400c0 > > Call Trace: > > [] dump_stack+0x4c/0x6e > > [] warn_slowpath_common+0x97/0xe0 > > [] warn_slowpath_fmt+0x46/0x50 > > [] i915_gem_free_object+0x2de/0x300 [i915] > > [] drm_gem_object_free+0x27/0x30 [drm] > > [] intel_user_framebuffer_destroy+0x75/0xa0 [i915] > > [] drm_framebuffer_free+0x5b/0x70 [drm] > > [] drm_framebuffer_unreference+0x39/0x70 [drm] > > [] drm_mode_set_config_internal+0xcc/0x110 [drm] > > [] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] > > [] drm_fb_helper_restore_fbdev_mode_unlocked+0x30/0x80 [drm_kms_helper] > > [] drm_fb_helper_set_par+0x24/0x50 [drm_kms_helper] > > [] intel_fbdev_set_par+0x1a/0x60 [i915] > > [] fbcon_init+0x514/0x5a0 > > [] visual_init+0xbc/0x120 > > [] do_bind_con_driver+0x16a/0x320 > > [] do_take_over_console+0x124/0x1d0 > > [] do_fbcon_takeover+0x5b/0xb0 > > [] fbcon_event_notify+0x672/0x800 > > [] notifier_call_chain+0x4d/0x70 > > [] __blocking_notifier_call_chain+0x58/0x80 > > [] blocking_notifier_call_chain+0x16/0x20 > > [] fb_notifier_call_chain+0x1b/0x20 > > [] register_framebuffer+0x1eb/0x320 > > [] drm_fb_helper_initial_config+0x214/0x3a0 [drm_kms_helper] > > [] intel_fbdev_initial_config+0x1b/0x20 [i915] > > [] async_run_entry_fn+0x4c/0x160 > > [] process_one_work+0x14b/0x4a0 > > [] worker_thread+0x11b/0x480 > > [] ? rescuer_thread+0x310/0x310 > > [] kthread+0xc9/0xe0 > > [] ? wq_unbind_fn+0xa0/0x100 > > [] ? flush_kthread_worker+0x90/0x90 > > [] ret_from_fork+0x7c/0xb0 > > [] ? flush_kthread_worker+0x90/0x90 > > ---[ end trace 507288b4d65403f3 ]--- > > > > It's not connected to a monitor so I don't know if it has a blank screen or not. > > But because of the warning, it makes my tests fail (ktest fails or call traces > > like this). > > > > I bisected it down to this commit: > > > > commit 455a68086d1dfb801ad7c867d5ca0ed0e0f758b0 > > Author: Gustavo Padovan > > Date: Mon Dec 1 15:40:11 2014 -0800 > > > > drm/i915: remove intel_pipe_set_base() (v4) > > > > > > -- Steve > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch