Attachment #96294
Move all ring resets before setting the HWS patch patch 2014-03-24 15:12:19 UTC 3.53 KB no flags Details
Attachment #96298
Xorg.0.log from the broken resume (with Chris' patch applied on top of drm-intel-testing). text/plain 2014-03-24 16:56:22 UTC 54.35 KB no flags Details
Attachment #96304
Explicitly stop the rings before resetting patch 2014-03-24 17:38:11 UTC 3.34 KB no flags Details
Attachment #96305
dmesg with drm.debug=7 application/octet-stream 2014-03-24 17:48:17 UTC 280.20 KB no flags Details

Attachment cannot be viewed because its MIME type is not text/*, image/*, or application/vnd.mozilla.*. Download the attachment instead.

Attachment #96307
Mark device as wedged if we fail to resume patch 2014-03-24 17:58:32 UTC 1023 bytes no flags Details
Attachment #96311
dmesg-2 application/octet-stream 2014-03-24 18:48:34 UTC 178.25 KB no flags Details

Attachment cannot be viewed because its MIME type is not text/*, image/*, or application/vnd.mozilla.*. Download the attachment instead.

Attachment #96323
Report EIO after resume failure in execbuffer patch 2014-03-24 21:17:54 UTC 1.73 KB no flags Details
Attachment #96406
Preserve ring buffers across resume patch 2014-03-26 11:47:29 UTC 8.71 KB no flags Details
Attachment #96776
drm.debug=7 dmesg with patched kernel text/plain 2014-04-02 11:46:14 UTC 138.96 KB no flags Details
Attachment #96783
drm.debug=7 dmesg with patched kernel (cfa8aaa3) text/plain 2014-04-02 13:43:29 UTC 260.45 KB no flags Details
Attachment #97027
Print ring registers for debugging patch 2014-04-07 09:25:28 UTC 1.41 KB no flags Details
Attachment #97034
dmesg with ring contets dump before/after initialization application/octet-stream 2014-04-07 11:33:46 UTC 18.60 KB no flags Details

Attachment cannot be viewed because its MIME type is not text/*, image/*, or application/vnd.mozilla.*. Download the attachment instead.

Attachment #97035
Poke the ring to see if it is awake patch 2014-04-07 11:45:19 UTC 933 bytes no flags Details
Attachment #97036
dmesg with ring contents dump and MI_NOOP writes issued application/octet-stream 2014-04-07 11:57:01 UTC 18.97 KB no flags Details

Attachment cannot be viewed because its MIME type is not text/*, image/*, or application/vnd.mozilla.*. Download the attachment instead.

Attachment #97739
dmesg with all the patches up to now applied text/plain 2014-04-22 11:23:05 UTC 70.88 KB no flags Details
Attachment #97744
dmesg with HEAD==218bb0e7f text/plain 2014-04-22 12:32:25 UTC 70.94 KB no flags Details
Attachment #97747
dmesg with fixed start/head text/plain 2014-04-22 13:55:57 UTC 80.96 KB no flags Details
Attachment #97756
Retry ring initialisation patch 2014-04-22 15:47:07 UTC 1.60 KB no flags Details
Attachment #97774
dmesg with retry-patch applied text/plain 2014-04-22 20:49:34 UTC 74.34 KB no flags Details
Attachment #99172
Prevent updating the HWS whilst it is active patch 2014-05-16 20:01:09 UTC 1.26 KB no flags Details
Attachment #104181
frob ring_stop a bit patch 2014-08-06 21:43:37 UTC 999 bytes no flags Details
Attachment #104208
frob + debug ring head patch 2014-08-07 08:54:30 UTC 2.53 KB no flags Details
Attachment #104212
dmesg with patch from comment #80 text/plain 2014-08-07 09:31:02 UTC 79.86 KB no flags Details
Attachment #104216
dmesg of 3.16 + patch from comment #80 text/plain 2014-08-07 09:51:47 UTC 74.05 KB no flags Details
Attachment #104224
[PATCH] drm/i915: read HEAD register back in init_ring_common() to enforce ordering patch 2014-08-07 12:22:29 UTC 1.19 KB no flags Details
Attachment #104226
dmesg with the frob+debug patch from comment #80 showing the issue patch 2014-08-07 13:46:19 UTC 101.18 KB no flags Details
Attachment #104227
head start before enabling patch 2014-08-07 14:04:18 UTC 1.12 KB no flags Details
Attachment #106514
dmesg 3.16.2 text/plain 2014-09-18 16:33:06 UTC 151.76 KB no flags Details
Attachment #107730
Extended-Revert-drm-i915-Move-all-ring-resets-before-setting-the-HWS-page.patch text/plain 2014-10-12 01:44:42 UTC 5.87 KB no flags Details

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.