diff mbox

drm/i915: info level for simulated gpu hang dmesg notice

Message ID 1365257318-22917-1-git-send-email-daniel.vetter@ffwll.ch (mailing list archive)
State New, archived
Headers show

Commit Message

Daniel Vetter April 6, 2013, 2:08 p.m. UTC
Otherwise running igt will fill your dmesg with hang notices and it's
hard to judge from a quick look whether they're expected or not.

Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
---
 drivers/gpu/drm/i915/i915_drv.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Chris Wilson April 8, 2013, 10:05 a.m. UTC | #1
On Sat, Apr 06, 2013 at 04:08:38PM +0200, Daniel Vetter wrote:
> Otherwise running igt will fill your dmesg with hang notices and it's
> hard to judge from a quick look whether they're expected or not.
> 
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Is there not a mechanism for userspace to inject messages into the
kernel message log? That would be far more useful...
-Chris
diff mbox

Patch

diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index a5b8aa9..3b4b9c0 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -822,7 +822,7 @@  int intel_gpu_reset(struct drm_device *dev)
 
 	/* Also reset the gpu hangman. */
 	if (dev_priv->gpu_error.stop_rings) {
-		DRM_DEBUG("Simulated gpu hang, resetting stop_rings\n");
+		DRM_INFO("Simulated gpu hang, resetting stop_rings\n");
 		dev_priv->gpu_error.stop_rings = 0;
 		if (ret == -ENODEV) {
 			DRM_ERROR("Reset not implemented, but ignoring "