Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit f4689801 authored by Daniel Vetter's avatar Daniel Vetter
Browse files

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 <ben@bwidawsk.net>
Acked-by: default avatarBen Widawsky <ben@bwidawsk.net>
[danvet: Frob the message as suggested by Paulo on irc.]
Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
parent 5c9669ce

drivers/gpu/drm/i915/i915_gpu_error.c

+6 −2
Original line number Diff line number Diff line
@@ -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);