Dave,
we discussed this on irc a week or so ago.
The traces we get from the kernel like
https://bugzilla.redhat.com/attachment.cgi?id=498312
aren't particularly useful, as we don't have any information on _why_ the
chip locked up, or even the last commands that caused it.
So this diff replaces the WARN so that we stop getting a backtrace.
This should stop abrt from automatically filing these bugs.
Is this palatable for upstream, or something you'd rather we just carry
in Fedora ?
Dave
diff --git a/drivers/gpu/drm/radeon/radeon_fence.c
b/drivers/gpu/drm/radeon/radeon_fence.c
index 7fd4e3e..a488b50 100644
--- a/drivers/gpu/drm/radeon/radeon_fence.c
+++ b/drivers/gpu/drm/radeon/radeon_fence.c
@@ -263,7 +263,7 @@ retry:
*/
if (seq == rdev->fence_drv.last_seq && radeon_gpu_is_lockup(rdev)) {
/* good news we believe it's a lockup */
- WARN(1, "GPU lockup (waiting for 0x%08X last fence id 0x%08X)\n",
+ printk(KERN_WARNING "GPU lockup (waiting for 0x%08X last fence id
0x%08X)\n",
fence->seq, seq);
/* FIXME: what should we do ? marking everyone
* as signaled for now