Chase Douglas wrote: > I've got two framebuffers and batchbuffers set up, but I'm having > problems trying to send two batchbuffers to DRM. If I try, using a > second call to drmCommandWrite in intel_batch_ioctl, I get kernel drm > errors such as: > > [drm:drm_fence_lazy_wait] *ERROR* Fence timeout. GPU lockup or fence > driver was taken down. > [drm:drm_bo_expire_fence] *ERROR* Detected GPU lockup or fence driver > was taken down. Evicting buffer. > > And then the card is usually hosed enough I need to reboot. I don't > really know anything about fences, and looking through the code hasn't > helped too much. Can anyone explain what's going on? I'm not sure it has really anything to do with the fence (probably could if it's set up wrongly) - maybe it's just the first thing to notice that the gpu has locked up. gpu lockups are not easy to debug, you need to figure out what was wrong with the commands you sent to the gpu.
Roland ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
