From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752247AbbGNMlq (ORCPT <rfc822;w@1wt.eu>);
	Tue, 14 Jul 2015 08:41:46 -0400
Received: from mail-wi0-f178.google.com ([209.85.212.178]:35287 "EHLO
	mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751674AbbGNMlo (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 14 Jul 2015 08:41:44 -0400
Date: Tue, 14 Jul 2015 14:44:25 +0200
From: Daniel Vetter <daniel@ffwll.ch>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: David Airlie <airlied@linux.ie>, intel-gfx@lists.freedesktop.org,
        dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb
Message-ID: <20150714124425.GZ3736@phenom.ffwll.local>
Mail-Followup-To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	David Airlie <airlied@linux.ie>, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
References: <20150713125139.GA562@swordfish>
 <20150713143549.GM3736@phenom.ffwll.local>
 <20150713144415.GA27052@swordfish>
 <20150713150506.GW3736@phenom.ffwll.local>
 <20150714113950.GA389@swordfish>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150714113950.GA389@swordfish>
X-Operating-System: Linux phenom 4.2.0-rc1+ 
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Jul 14, 2015 at 08:39:50PM +0900, Sergey Senozhatsky wrote:
> On (07/13/15 17:05), Daniel Vetter wrote:
> > It goes boom somewhere from the cursor ioctl code, which means X is
> > probably involved. Usual suspects are vt-switching, suspend/resume or
> > cursor vs. DPMS. You can force a DPMS off from within X with
> > 
> > $ xset dpms force off
> > 
> 
> that helped. seems to be working only on -next.

You mean you only get a backtrace on -next, right? Otherwise I'd be
confused ;-)

Next up. Please boot with drm.debug=0xe, repro the issue and attach
complete dmesg (from boot-up up to the WARNING). That should help us
reconstruct how things went wrong here.

Thanks, Daniel

> 
> [   42.409154] ------------[ cut here ]------------
> [   42.409234] WARNING: CPU: 0 PID: 359 at drivers/gpu/drm/i915/i915_gem.c:5368 i915_gem_track_fb+0xdc/0x106 [i915]()
> [   42.409239] WARN_ON(new->frontbuffer_bits & frontbuffer_bits)
> [   42.409243] Modules linked in:
> [   42.409248]  sha256_ssse3 sha256_generic hmac drbg ctr ccm mousedev arc4 nls_iso8859_1 nls_cp437 coretemp vfat hwmon iwlmvm fat intel_powerclamp crc32c_intel i915 mac80211 psmouse i2c_i801 cfbfillrect cfbimgblt iwlwifi i2c_algo_bit serio_raw cfbcopyarea ie31200_edac lpc_ich atkbd r8169 libps2 mfd_core drm_kms_helper cfg80211 mii drm edac_core thermal mxm_wmi i8042 video serio backlight wmi evdev processor ext4 crc16 mbcache jbd2 sd_mod ehci_pci ehci_hcd ahci libahci libata xhci_pci xhci_hcd scsi_mod usbcore usb_common
> [   42.409364] CPU: 0 PID: 359 Comm: Xorg Not tainted 4.2.0-rc2-next-20150713-dbg-00017-g16b87ed-dirty #183
> [   42.409369]  0000000000000009 ffff88041ce139d8 ffffffff813a19ac ffffffff81077163
> [   42.409379]  ffff88041ce13a28 ffff88041ce13a18 ffffffff8103b5d9 ffff88041ce139f8
> [   42.409388]  ffffffffa054b273 0000000000000002 ffff88041a938240 ffff88041a938240
> [   42.409397] Call Trace:
> [   42.409414]  [<ffffffff813a19ac>] dump_stack+0x4c/0x65
> [   42.409425]  [<ffffffff81077163>] ? up+0x39/0x3e
> [   42.409433]  [<ffffffff8103b5d9>] warn_slowpath_common+0x9b/0xb5
> [   42.409486]  [<ffffffffa054b273>] ? i915_gem_track_fb+0xdc/0x106 [i915]
> [   42.409492]  [<ffffffff8103b639>] warn_slowpath_fmt+0x46/0x48
> [   42.409540]  [<ffffffffa054b273>] i915_gem_track_fb+0xdc/0x106 [i915]
> [   42.409611]  [<ffffffffa058d928>] intel_prepare_plane_fb+0xb1/0x101 [i915]
> [   42.409632]  [<ffffffffa027ff0f>] drm_atomic_helper_prepare_planes+0x5b/0xb8 [drm_kms_helper]
> [   42.409700]  [<ffffffffa059d596>] intel_atomic_commit+0x46/0xc0 [i915]
> [   42.409750]  [<ffffffffa02f2139>] drm_atomic_commit+0x4d/0x52 [drm]
> [   42.409769]  [<ffffffffa0280f32>] drm_atomic_helper_update_plane+0xca/0x119 [drm_kms_helper]
> [   42.409811]  [<ffffffffa02e7572>] __setplane_internal+0x24e/0x2ae [drm]
> [   42.409846]  [<ffffffffa02e771b>] drm_mode_cursor_universal+0x149/0x197 [drm]
> [   42.409880]  [<ffffffffa02e7e58>] ? drm_mode_setcrtc+0x428/0x428 [drm]
> [   42.409910]  [<ffffffffa02e781e>] drm_mode_cursor_common+0xb5/0x156 [drm]
> [   42.409939]  [<ffffffffa02e7e8f>] drm_mode_cursor_ioctl+0x37/0x39 [drm]
> [   42.409967]  [<ffffffffa02dae85>] drm_ioctl+0x287/0x415 [drm]
> [   42.409975]  [<ffffffff81078580>] ? __lock_is_held+0x3c/0x57
> [   42.409983]  [<ffffffff8114c3d1>] ? __fget+0x170/0x1a1
> [   42.409991]  [<ffffffff811422c1>] do_vfs_ioctl+0x455/0x4dd
> [   42.409996]  [<ffffffff8114c48e>] ? __fget_light+0x65/0x75
> [   42.410003]  [<ffffffff8114238d>] SyS_ioctl+0x44/0x63
> [   42.410010]  [<ffffffff813a8057>] entry_SYSCALL_64_fastpath+0x12/0x6f
> [   42.410016] ---[ end trace 90f0a9050a7baa50 ]---
> 
> 	-ss
> 
> > For suspend resume it occasionally matters whether you initiate it through
> > the gui or by closing the lid or through timeout (if you're not connected
> > to a wallplug). I hope this helps with figuring out a repro recipe.
> > 
> > It could also be a race somewhere, in which case you won't be able to
> > consistently reproduce this.
> _______________________________________________
> 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