Bug 106634

Summary: Failed to find memory space for buffer [...] eviction
Product: DRI Reporter: udo <udovdh>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: majewsky
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg
none
messages
none
xorg log
none
Print fpfn/lpfn values in ttm_bo_mem_space_debug
none
journal none

Description udo 2018-05-23 15:49:18 UTC
Created attachment 139715 [details]
dmesg

Gigabyte X470-AORUS-ULTRA-GAMING board with AMD Ryzen 5 2400g APU, Fedora 28, git MESA, git AMDGPU; box was migrated today from AMD A10-5800 based solution.

I found these in xorg.log:

[  1894.583] (WW) AMDGPU(0): flip queue failed: Cannot allocate memory
[  1894.583] (WW) AMDGPU(0): Page flip failed: Cannot allocate memory
[  1894.583] (EE) AMDGPU(0): present flip failed
[  1894.594] (WW) AMDGPU(0): flip queue failed in amdgpu_scanout_flip: Cannot allocate memory, TearFree inactive until next modeset
Comment 1 udo 2018-05-23 15:49:42 UTC
Created attachment 139716 [details]
messages
Comment 2 udo 2018-05-23 15:58:14 UTC
Created attachment 139717 [details]
xorg log
Comment 3 Michel Dänzer 2018-05-23 16:06:49 UTC
Please also attach the dmesg output from before the problem occurs, containing at least all the amdgpu and TTM initialization messages.
Comment 4 Michel Dänzer 2018-05-23 16:16:22 UTC
Created attachment 139718 [details] [review]
Print fpfn/lpfn values in ttm_bo_mem_space_debug

Can you rebuild the ttm.ko module with this patch applied, and attach the resulting dmesg output when the problem occurs again? It might shed some more light on why we fail to evict a BO to GTT, even though there seems to be enough space there.
Comment 5 udo 2018-05-23 16:22:11 UTC
There is no dmesg from before the problem occurs.
I will try the patch!
Comment 6 udo 2018-05-23 16:32:57 UTC
Created attachment 139719 [details]
journal
Comment 7 Michel Dänzer 2018-05-23 16:46:53 UTC
Actually, it seems clear that this happens because 1 GB of VRAM and 3 GB of GTT are full with buffer objects. Unless this keeps happening even immediately after closing applications / logging out and back in / restarting X, this looks like a userspace issue (could be a leak somewhere).
Comment 8 Martin Peres 2019-11-19 08:39:06 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/394.

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.