From: Nikola Pajkovsky <npajkovs@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: WARNING: at drivers/gpu/drm/i915/i915_gem.c:3437 i915_gem_object_pin+0x151/0x1a0()
Date: Tue, 11 Dec 2012 13:31:36 +0100 [thread overview]
Message-ID: <87vcc8vkgn.fsf@redhat.com> (raw)
Hey folks,
looks like we still have some oops in i915. i915 maintainers do you have
any ideas what's going on? I will try to trigger that oops later today
and provide more information.
[10733.442608] WARNING: at drivers/gpu/drm/i915/i915_gem.c:3437 i915_gem_object_pin+0x151/0x1a0()
[10733.442612] Hardware name: 4243BQ9
[10733.442615] Modules linked in: kvm_intel kvm
[10733.442632] Pid: 1361, comm: X Not tainted 3.7.0 #19
[10733.442635] Call Trace:
[10733.442650] [<ffffffff81095efa>] warn_slowpath_common+0x7a/0xb0
[10733.442659] [<ffffffff81095f45>] warn_slowpath_null+0x15/0x20
[10733.442669] [<ffffffff814dc041>] i915_gem_object_pin+0x151/0x1a0
[10733.442679] [<ffffffff814dc0ea>] i915_gem_object_pin_to_display_plane+0x5a/0x90
[10733.442689] [<ffffffff814d80f5>] ? i915_mutex_lock_interruptible+0x35/0xc0
[10733.442700] [<ffffffff814ec6b0>] intel_pin_and_fence_fb_obj+0x50/0x130
[10733.442709] [<ffffffff814ec9de>] intel_gen6_queue_flip+0x3e/0x160
[10733.442719] [<ffffffff814f01f2>] intel_crtc_page_flip+0x1d2/0x370
[10733.442728] [<ffffffff814bd633>] drm_mode_page_flip_ioctl+0x273/0x300
[10733.442738] [<ffffffff814aba20>] drm_ioctl+0x2d0/0x520
[10733.442746] [<ffffffff814bd3c0>] ? drm_mode_gamma_get_ioctl+0x120/0x120
[10733.442757] [<ffffffff818d172f>] ? _raw_spin_unlock_irqrestore+0x5f/0x70
[10733.442768] [<ffffffff810a4321>] ? del_timer+0x61/0x90
[10733.442779] [<ffffffff8111fc34>] ? rcu_cleanup_after_idle+0x24/0x40
[10733.442829] [<ffffffff811205b6>] ? rcu_prepare_for_idle+0x1b6/0x300
[10733.442838] [<ffffffff81121d89>] ? rcu_user_exit+0x69/0xc0
[10733.442847] [<ffffffff8119eafa>] do_vfs_ioctl+0x8a/0x2f0
[10733.442859] [<ffffffff810ebfbd>] ? trace_hardirqs_on+0xd/0x10
[10733.442866] [<ffffffff8119edf1>] sys_ioctl+0x91/0xa0
[10733.442876] [<ffffffff818d8d18>] tracesys+0xe1/0xe6
--
Nikola
next reply other threads:[~2012-12-11 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 12:31 Nikola Pajkovsky [this message]
2012-12-11 15:08 ` WARNING: at drivers/gpu/drm/i915/i915_gem.c:3437 i915_gem_object_pin+0x151/0x1a0() Daniel Vetter
2012-12-11 15:31 ` Nikola Pajkovsky
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=87vcc8vkgn.fsf@redhat.com \
--to=npajkovs@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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.