<b>Chrome Version: <From about:version: Google Chrome x.x.x.x></b>
<b>Chrome OS Version: <From about:version: Platform x.x.x.x></b>
<b>Chrome OS Platform: <Make/model of computer running Chrome OS></b>
<b>Network info: <network, encryption type, router model (if known)></b>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)  build glimmer-cheets image, and boot on glimmer board 
(2)  suspend_stress_test -c 5000 --noerrors_fatal --record_dmesg_dir=./logs 
(3)  Check dmesg logs for failed iterations in ./logs directory.
(4)

Expected Result:
No failures at suspend.

Actual Result:

i915_drv failure here. Looks like a timeout in vlv_suspend_complete, vlv_force_gfx_clock 

[ 9253.639684] calling  0000:00:02.0+ @ 1508, parent: pci0000:00
[ 9253.661775] [drm:vlv_force_gfx_clock] *ERROR* timeout waiting for GFX clock force-on (00000004)
[ 9253.661786] [drm:i915_drm_suspend_late] *ERROR* Suspend complete failed: -110
[ 9253.754211] dpm_run_callback(): i915_pm_suspend_late+0x0/0x2b returns -110
[ 9253.754220] call 0000:00:02.0+ returned -110 after 111752 usecs

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
I had 3 failures in about 300 iterations.

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.
Logs attached.

 

Deleted: dmesg_54 31.0 KB

dmesg_54 31.0 KB View Download

Deleted: dmesg_188 31.0 KB

dmesg_188 31.0 KB View Download

Deleted: dmesg_267 31.0 KB

dmesg_267 31.0 KB View Download