From: Daniel Vetter Date: Wed, 9 Oct 2013 17:22:22 +0000 (+0200) Subject: drm/i915: Educate users in dmesg about reporting gpu hangs X-Git-Tag: v3.13-rc1~69^2~3^2~132 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f468980171fa6293917a8b59bfec71c6616e06c9;p=platform%2Fkernel%2Flinux-stable.git drm/i915: Educate users in dmesg about reporting gpu hangs Untangling me-too reports that actually aren't is really messy. And we need to make sure the blame is put where it should be right from the start ;-) v2: Improve the wording from Ben's suggestions. Cc: Ben Widawsky Acked-by: Ben Widawsky [danvet: Frob the message as suggested by Paulo on irc.] Signed-off-by: Daniel Vetter --- diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c index 915c8ca..5dde810 100644 --- a/drivers/gpu/drm/i915/i915_gpu_error.c +++ b/drivers/gpu/drm/i915/i915_gpu_error.c @@ -910,8 +910,12 @@ void i915_capture_error_state(struct drm_device *dev) return; } - DRM_INFO("capturing error event; look for more information in " - "/sys/class/drm/card%d/error\n", dev->primary->index); + DRM_INFO("GPU crash dump saved to /sys/class/drm/card%d/error\n", + dev->primary->index); + DRM_INFO("GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.\n"); + DRM_INFO("Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel\n"); + DRM_INFO("drm/i915 developers can then reassign to the right component if it's not a kernel issue.\n"); + DRM_INFO("The gpu crash dump is required to analyze gpu hangs, so please always attach it.\n"); kref_init(&error->ref); error->eir = I915_READ(EIR);