Subject : [drm:init_ring_common] *ERROR* render ring head not reset to zero
Submitter : Thomas Meyer <firstname.lastname@example.org>
Date : 2010-10-04 20:31
Message-ID : email@example.com
References : http://marc.info/?l=linux-kernel&m=128622441331199&w=2
This entry is being used for tracking a regression from 2.6.35. Please don't
close it until the problem is fixed in the mainline.
The hardware reset on the second attempt, so I am treating this as an overzealous warning. According to the code comments, gm45 is known to be prone to failing to reset on the first attempt.
Author: Chris Wilson <firstname.lastname@example.org>
Date: Sun Dec 5 20:42:33 2010 +0000
drm/i915/ringbuffer: Only print an error on the second attempt to reset he
There's not much we can do here but hope for the best. However the first
failure happens quite frequently and if often remedied by the second
attempt to reset HEAD. So only print the error if that attempt also
Reported-by: Thomas Meyer <email@example.com>
Signed-off-by: Chris Wilson <firstname.lastname@example.org>
Created attachment 39152 [details]
drm/i915/ringbuffer: Only print an error on the second attempt to reset head
So my original question was: "Bug or feature?" So i guess the warning and/or error message is both! I could easily live with the error message...
Fixed by commit 6fd0d56 drm/i915/ringbuffer: Only print an error on the second attempt to reset head .