diff options
author | Chris Wilson <[email protected]> | 2014-04-09 09:19:43 +0100 |
---|---|---|
committer | Daniel Vetter <[email protected]> | 2014-05-05 09:08:39 +0200 |
commit | 074c6adaf4e7d1423d373bd5d1afc20b683cb4d0 (patch) | |
tree | b10e573b5f30f5571d6bff7e8cb1c1b7675a996e /tools/perf/scripts/python/net_dropmonitor.py | |
parent | 6099032045d4d83bf643b5fe33caaa8e56e7f5de (diff) |
drm/i915: Mark device as wedged if we fail to resume
During module load, if we fail to initialise the rings, we abort the
load reporting EIO. However during resume, even though we report EIO as
we fail to reinitialize the ringbuffers, the resume continues and the
device is restored - albeit in a non-functional state. As we cannot
execute any commands on the GPU, it is effectively wedged, mark it so.
As we now preserve the ringbuffers across resume, this should prevent
UXA from falling into the trap of repeatedly sending invalid
batchbuffers and dropping all further rendering into /dev/null.
Reported-and-tested-by: Jiri Kosina <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=76554
Signed-off-by: Chris Wilson <[email protected]>
Reviewed-by: Oscar Mateo <[email protected]>
[danvet: Drop unused error, spotted by Oscar.]
Signed-off-by: Daniel Vetter <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions