Attachment #107325
dmesg on bad commit text/plain 2014-10-04 14:51:41 UTC 55.21 KB no flags Details
Attachment #107326
gallium hud on good - longer pause matches bump on vram/gtt graphs image/png 2014-10-04 14:57:10 UTC 1.40 MB no flags Details
Attachment #107327
gallium hud on bad showing different vram gtt usage image/png 2014-10-04 14:58:41 UTC 1.40 MB no flags Details
Attachment #107391
Make Mesa behave as if the kernel was older patch 2014-10-06 07:24:18 UTC 1.05 KB no flags Details
Attachment #107438
bad gtt usage (Borderlands 2) image/png 2014-10-06 16:59:03 UTC 2.86 MB no flags Details
Attachment #107451
ttm: Don't evict BOs outside of requested placement range patch 2014-10-07 03:47:36 UTC 1.67 KB no flags Details
Attachment #107493
vram usage with Don't evict BOs outside of requested placement range image/png 2014-10-07 13:17:01 UTC 1.38 MB no flags Details
Attachment #107542
r600g,radeonsi: Use staging texture for transfers if any miplevel is tiled patch 2014-10-08 08:03:26 UTC 945 bytes no flags Details
Attachment #107543
winsys/radeon: Use separate caching buffer manager for each set of flags patch 2014-10-08 08:04:19 UTC 5.81 KB no flags Details
Attachment #107544
drm/radeon: Try placing NO_CPU_ACCESS BOs outside of CPU accessible VRAM patch 2014-10-08 08:06:44 UTC 2.88 KB no flags Details
Attachment #107560
Hud with 2 kernel and 2 mesa patches better but still bad. image/png 2014-10-08 15:22:17 UTC 1.39 MB no flags Details
Attachment #107863
Kernel errors with mesa patched + agd5f drm-next-3.19 text/plain 2014-10-15 09:55:10 UTC 91.33 KB no flags Details
Attachment #108866
new issue long pause at end of demo image/png 2014-11-03 22:03:24 UTC 647.54 KB no flags Details
Attachment #111191
dmesg while playing L4D2 on a RV770 with kernel 3.17.7 text/plain 2014-12-22 21:54:04 UTC 10.06 KB no flags Details
Attachment #111966
elemental stalls near end with large vram -> gtt move image/png 2015-01-08 17:30:32 UTC 986.82 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.