From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Joakim Hernberg <jbh@alchemy.lu>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 3.8.4-rt2: (x86_64): BUG: scheduling while atomic
Date: Thu, 25 Apr 2013 17:50:18 +0200 [thread overview]
Message-ID: <20130425155018.GB5561@linutronix.de> (raw)
In-Reply-To: <20130327131658.22aef026@tor.valhalla.alchemy.lu>
* Joakim Hernberg | 2013-03-27 13:16:58 [+0100]:
>[ 618.783525] BUG: scheduling while atomic: X/630/0x00000003
>[ 618.783597] [<ffffffffa00b2a33>] ftrace_raw_event_i915_gem_ring_dispatch+0xe3/0x100 [i915]
Please format your backtrace properl next time.
Can you re-produce this? If so, does this help:
diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
index 26d08bb..7d56265 100644
--- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
+++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
@@ -1064,6 +1064,7 @@ i915_gem_do_execbuffer(struct drm_device *dev, void *data,
}
trace_i915_gem_ring_dispatch(ring, intel_ring_get_seqno(ring), flags);
+ i915_trace_irq_get(ring, seqno);
i915_gem_execbuffer_move_to_active(&objects, ring);
i915_gem_execbuffer_retire_commands(dev, file, ring);
diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
index 3db4a68..29217db 100644
--- a/drivers/gpu/drm/i915/i915_trace.h
+++ b/drivers/gpu/drm/i915/i915_trace.h
@@ -244,7 +244,6 @@ TRACE_EVENT(i915_gem_ring_dispatch,
__entry->ring = ring->id;
__entry->seqno = seqno;
__entry->flags = flags;
- i915_trace_irq_get(ring, seqno);
),
TP_printk("dev=%u, ring=%u, seqno=%u, flags=%x",
Sebastian
prev parent reply other threads:[~2013-04-25 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:16 3.8.4-rt2: (x86_64): BUG: scheduling while atomic Joakim Hernberg
2013-04-25 15:50 ` Sebastian Andrzej Siewior [this message]
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=20130425155018.GB5561@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jbh@alchemy.lu \
--cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).