#774899 libdrm-intel1: 855GM: Failed to submit batch buffer, expect rendering corruption: No space left on device #774899
- Package:
- libdrm-intel1
- Source:
- libdrm
- Description:
- Userspace interface to intel-specific kernel DRM services -- runtime
- Submitter:
- Matthias GroÃmann
- Date:
- 2023-11-08 14:48:03 UTC
- Severity:
- normal
- Tags:
Dear Maintainer, since upgrading my ThinkPad X40 (Intel 855GM graphics) to Jessie, the following error message appeares about twice a week in Xorg.0.log: [ 5173.704] (EE) intel(0): Failed to submit batch buffer, expect rendering corruption: No space left on device. After this, newly opened windows or menus are either filled in black or show up as empty frames until I reboot or disable KDE's desktop effects. So far, I have not been able to trigger this bug reliably, but this typically happens when iceweasel displays large images. By adding some fprintfs to the source code, I was able to track the problem down to drm_intel_gem_check_aperture_space() in libdrm-2.4.58/intel/intel_bufmgr_gem.c. This function returned -ENOSPC because total_fences==7 and bufmgr_gem->available_fences==6. There is a report for a similar bug (#725781), which was fixed upstream (https://bugs.freedesktop.org/show_bug.cgi?id=59771#c29). If you think there is a chance that this patch fixes my problem too, I'm going to test it.
I applied the patch (ec65f8d71eb3eb065c7cadf4153138435ac3b388), but unfortunately, this did not fix this bug.
wrong. As it turned out, this function fails a lot more often than I see the "failed to submit batch buffer" message in Xorg.0.log - in general without any noticeable impact. After enabling some more debug output, I am now seeing the error message Execbuffer fails to pin. Estimate: 234897408. Actual: 67125248. Available: 130940928 so I guess that the DRM_IOCTL_I915_GEM_EXECBUFFER2 ioctl in do_exec2() causes the failure. LibreOffice's print dialog can (sometimes) also trigger this bug.
Control: tag -1 = upstream moreinfo I realize this is a very old bug and I'm wondering whether the issue is still present. Can you check and report back (including with which versions you tested)?