dirty suspend after piglit run

[Tom St Denis]

On my Carrizo with the tip of drm-next as of today I get VM faults near 
the end of the piglit tests (with "-x max.*size") which then manifest 
UVD problems when decoding with a system suspend in the middle.

Attached is the dmesg log.

Suspend works fine if I don't trigger the VM faults first.

I'll see if I can bisect down the VM faults since I think this is a 
relatively new regression (with max.*size excluded).

Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: carrizo_after_piglit_then_after_suspend_with_uvd.log
Type: text/x-log
Size: 99000 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20171116/9d697c42/attachment-0001.bin>