From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [-next] WARNING at i915_gem_track_fb
Date: Mon, 13 Jul 2015 23:57:40 +0900 [thread overview]
Message-ID: <20150713145740.GA628@swordfish> (raw)
In-Reply-To: <55A3CF29.3010006@linux.intel.com>
On (07/13/15 16:46), Maarten Lankhorst wrote:
> > [ 1239.783961] [<ffffffff813a19ac>] dump_stack+0x4c/0x65
> > [ 1239.783965] [<ffffffff81077163>] ? up+0x39/0x3e
> > [ 1239.783968] [<ffffffff8103b5d9>] warn_slowpath_common+0x9b/0xb5
> > [ 1239.783986] [<ffffffffa0533273>] ? i915_gem_track_fb+0xdc/0x106 [i915]
> > [ 1239.783987] [<ffffffff8103b639>] warn_slowpath_fmt+0x46/0x48
> > [ 1239.784002] [<ffffffffa0533273>] i915_gem_track_fb+0xdc/0x106 [i915]
> > [ 1239.784026] [<ffffffffa0575928>] intel_prepare_plane_fb+0xb1/0x101 [i915]
> > [ 1239.784033] [<ffffffffa0261f0f>] drm_atomic_helper_prepare_planes+0x5b/0xb8 [drm_kms_helper]
> > [ 1239.784055] [<ffffffffa0585596>] intel_atomic_commit+0x46/0xc0 [i915]
> > [ 1239.784072] [<ffffffffa02d2139>] drm_atomic_commit+0x4d/0x52 [drm]
> > [ 1239.784078] [<ffffffffa0262f32>] drm_atomic_helper_update_plane+0xca/0x119 [drm_kms_helper]
> > [ 1239.784092] [<ffffffffa02c7572>] __setplane_internal+0x24e/0x2ae [drm]
> > [ 1239.784103] [<ffffffffa02c771b>] drm_mode_cursor_universal+0x149/0x197 [drm]
> > [ 1239.784113] [<ffffffffa02c7e58>] ? drm_mode_setcrtc+0x428/0x428 [drm]
> > [ 1239.784122] [<ffffffffa02c781e>] drm_mode_cursor_common+0xb5/0x156 [drm]
> > [ 1239.784132] [<ffffffffa02c7e8f>] drm_mode_cursor_ioctl+0x37/0x39 [drm]
> > [ 1239.784140] [<ffffffffa02bae85>] drm_ioctl+0x287/0x415 [drm]
> > [ 1239.784143] [<ffffffff81078580>] ? __lock_is_held+0x3c/0x57
> > [ 1239.784146] [<ffffffff8114c3d1>] ? __fget+0x170/0x1a1
> > [ 1239.784148] [<ffffffff811422c1>] do_vfs_ioctl+0x455/0x4dd
> > [ 1239.784151] [<ffffffff8114c48e>] ? __fget_light+0x65/0x75
> > [ 1239.784153] [<ffffffff8114238d>] SyS_ioctl+0x44/0x63
> > [ 1239.784155] [<ffffffff813a8057>] entry_SYSCALL_64_fastpath+0x12/0x6f
> > [ 1239.784157] ---[ end trace 67b32b389e7fe7df ]---
> >
> Do you have some steps to reproduce?
>
Unfortunately no.
-ss
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
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
Date: Mon, 13 Jul 2015 23:57:40 +0900 [thread overview]
Message-ID: <20150713145740.GA628@swordfish> (raw)
In-Reply-To: <55A3CF29.3010006@linux.intel.com>
On (07/13/15 16:46), Maarten Lankhorst wrote:
> > [ 1239.783961] [<ffffffff813a19ac>] dump_stack+0x4c/0x65
> > [ 1239.783965] [<ffffffff81077163>] ? up+0x39/0x3e
> > [ 1239.783968] [<ffffffff8103b5d9>] warn_slowpath_common+0x9b/0xb5
> > [ 1239.783986] [<ffffffffa0533273>] ? i915_gem_track_fb+0xdc/0x106 [i915]
> > [ 1239.783987] [<ffffffff8103b639>] warn_slowpath_fmt+0x46/0x48
> > [ 1239.784002] [<ffffffffa0533273>] i915_gem_track_fb+0xdc/0x106 [i915]
> > [ 1239.784026] [<ffffffffa0575928>] intel_prepare_plane_fb+0xb1/0x101 [i915]
> > [ 1239.784033] [<ffffffffa0261f0f>] drm_atomic_helper_prepare_planes+0x5b/0xb8 [drm_kms_helper]
> > [ 1239.784055] [<ffffffffa0585596>] intel_atomic_commit+0x46/0xc0 [i915]
> > [ 1239.784072] [<ffffffffa02d2139>] drm_atomic_commit+0x4d/0x52 [drm]
> > [ 1239.784078] [<ffffffffa0262f32>] drm_atomic_helper_update_plane+0xca/0x119 [drm_kms_helper]
> > [ 1239.784092] [<ffffffffa02c7572>] __setplane_internal+0x24e/0x2ae [drm]
> > [ 1239.784103] [<ffffffffa02c771b>] drm_mode_cursor_universal+0x149/0x197 [drm]
> > [ 1239.784113] [<ffffffffa02c7e58>] ? drm_mode_setcrtc+0x428/0x428 [drm]
> > [ 1239.784122] [<ffffffffa02c781e>] drm_mode_cursor_common+0xb5/0x156 [drm]
> > [ 1239.784132] [<ffffffffa02c7e8f>] drm_mode_cursor_ioctl+0x37/0x39 [drm]
> > [ 1239.784140] [<ffffffffa02bae85>] drm_ioctl+0x287/0x415 [drm]
> > [ 1239.784143] [<ffffffff81078580>] ? __lock_is_held+0x3c/0x57
> > [ 1239.784146] [<ffffffff8114c3d1>] ? __fget+0x170/0x1a1
> > [ 1239.784148] [<ffffffff811422c1>] do_vfs_ioctl+0x455/0x4dd
> > [ 1239.784151] [<ffffffff8114c48e>] ? __fget_light+0x65/0x75
> > [ 1239.784153] [<ffffffff8114238d>] SyS_ioctl+0x44/0x63
> > [ 1239.784155] [<ffffffff813a8057>] entry_SYSCALL_64_fastpath+0x12/0x6f
> > [ 1239.784157] ---[ end trace 67b32b389e7fe7df ]---
> >
> Do you have some steps to reproduce?
>
Unfortunately no.
-ss
next prev parent reply other threads:[~2015-07-13 14:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 12:51 [-next] WARNING at i915_gem_track_fb Sergey Senozhatsky
2015-07-13 12:51 ` Sergey Senozhatsky
2015-07-13 14:35 ` [Intel-gfx] " Daniel Vetter
2015-07-13 14:35 ` Daniel Vetter
2015-07-13 14:44 ` Sergey Senozhatsky
2015-07-13 14:44 ` [Intel-gfx] " Sergey Senozhatsky
2015-07-13 15:05 ` Daniel Vetter
2015-07-13 15:05 ` [Intel-gfx] " Daniel Vetter
2015-07-14 11:39 ` Sergey Senozhatsky
2015-07-14 11:39 ` Sergey Senozhatsky
2015-07-14 12:44 ` Daniel Vetter
2015-07-14 12:44 ` Daniel Vetter
2015-07-14 13:41 ` Sergey Senozhatsky
2015-07-14 13:41 ` [Intel-gfx] " Sergey Senozhatsky
2015-07-14 15:11 ` Daniel Vetter
2015-07-14 15:11 ` Daniel Vetter
2015-07-15 11:12 ` Sergey Senozhatsky
2015-07-15 11:12 ` Sergey Senozhatsky
2015-07-15 2:51 ` Michel Dänzer
2015-07-15 11:14 ` Sergey Senozhatsky
2015-07-15 11:14 ` Sergey Senozhatsky
2015-07-13 14:46 ` Maarten Lankhorst
2015-07-13 14:46 ` [Intel-gfx] " Maarten Lankhorst
2015-07-13 14:57 ` Sergey Senozhatsky [this message]
2015-07-13 14:57 ` Sergey Senozhatsky
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=20150713145740.GA628@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
/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.