System is a second generation Intel computestick running Ubuntu 16.04 and kernel version 4.10.0-33-generic. C-states have been disabled. "timed out waiting for forcewake ack request" is spammed, then GPU hangs while in a ROS gscam process. See attached files for dmesg log and error log.
Created attachment 133858 [details] GPU error
Created attachment 133859 [details] GPU error (2)
Created attachment 133860 [details] dmesg
Hmm, the video decoder is active at the time of the hang, so the forcewake errors may well be due to an invalid batch. It then screws up the gpu such that recovery is then impossible. Since the GPU is dead, the error state is devoid of register information, definitely an interesting side-effect! The second hang also points the finger at libva. It's worth just sticking on drm-tip [https://cgit.freedesktop.org/drm-tip] just to see if anything changes.
Update, from my end: Due to some software dependencies on our system, I'm hesitant to change the kernel version. I've done some research on the problem and found the Arch Linux community has reported 1915 issues with Skylake processors (https://wiki.archlinux.org/index.php/intel_graphics#Skylake_support). While this is a Debian/Ubuntu system, I tried their recommendation of setting i915.enable_rc6=0 in my grub configuration, which appears to resolve/suppress the GPU hangs,
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing, please re-open is issue still exists.
Forward dup to retain some history. *** This bug has been marked as a duplicate of bug 110297 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.