[Bug 106634] some memory issue

List overview All Threads
Download

newer

older

[Bug 70514] New: Unresponsive...

[Bug 70286] New: X crashes when...

bugzilla-daemon＠freedesktop.org

23 May 2018 23 May '18

3:49 p.m.

https://bugs.freedesktop.org/show_bug.cgi?id=106634

Bug ID: 106634 Summary: some memory issue Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: udovdh@xs4all.nl

Created attachment 139715 --> https://bugs.freedesktop.org/attachment.cgi?id=139715&action=edit 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

-- You are receiving this mail because: You are the assignee for the bug.

Attachments:

attachment.html (text/html — 2.3 KB)

Show replies by date

bugzilla-daemon＠freedesktop.org

23 May 23 May

3:49 p.m.

https://bugs.freedesktop.org/show_bug.cgi?id=106634

--- Comment #1 from udo udovdh@xs4all.nl --- Created attachment 139716 --> https://bugs.freedesktop.org/attachment.cgi?id=139716&action=edit messages

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

3:52 p.m.

New subject: [Bug 106634] flip queue failed: Cannot allocate memory

https://bugs.freedesktop.org/show_bug.cgi?id=106634

udo udovdh@xs4all.nl changed:

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

3:53 p.m.

New subject: [Bug 106634] flip queue failed in amdgpu_scanout_flip: Cannot allocate memory, TearFree inactive until next modeset

https://bugs.freedesktop.org/show_bug.cgi?id=106634

udo udovdh@xs4all.nl changed:

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

3:58 p.m.

New subject: [Bug 106634] flip queue failed in amdgpu_scanout_flip: Cannot allocate memory, TearFree inactive until next modeset

https://bugs.freedesktop.org/show_bug.cgi?id=106634

--- Comment #2 from udo udovdh@xs4all.nl --- Created attachment 139717 --> https://bugs.freedesktop.org/attachment.cgi?id=139717&action=edit xorg log

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

4:06 p.m.

New subject: [Bug 106634] Failed to find memory space for buffer [...] eviction

https://bugs.freedesktop.org/show_bug.cgi?id=106634

Michel Dänzer michel@daenzer.net changed:

--- Comment #3 from Michel Dänzer michel@daenzer.net --- Please also attach the dmesg output from before the problem occurs, containing at least all the amdgpu and TTM initialization messages.

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

4:16 p.m.

New subject: [Bug 106634] Failed to find memory space for buffer [...] eviction

https://bugs.freedesktop.org/show_bug.cgi?id=106634

--- Comment #4 from Michel Dänzer michel@daenzer.net --- Created attachment 139718 --> https://bugs.freedesktop.org/attachment.cgi?id=139718&action=edit 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.

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

4:22 p.m.

New subject: [Bug 106634] Failed to find memory space for buffer [...] eviction

https://bugs.freedesktop.org/show_bug.cgi?id=106634

--- Comment #5 from udo udovdh@xs4all.nl --- There is no dmesg from before the problem occurs. I will try the patch!

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

4:32 p.m.

New subject: [Bug 106634] Failed to find memory space for buffer [...] eviction

https://bugs.freedesktop.org/show_bug.cgi?id=106634

--- Comment #6 from udo udovdh@xs4all.nl --- Created attachment 139719 --> https://bugs.freedesktop.org/attachment.cgi?id=139719&action=edit journal

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

4:46 p.m.

New subject: [Bug 106634] Failed to find memory space for buffer [...] eviction

https://bugs.freedesktop.org/show_bug.cgi?id=106634

--- Comment #7 from Michel Dänzer michel@daenzer.net --- 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).

-- You are receiving this mail because: You are the assignee for the bug.

bugzilla-daemon＠freedesktop.org

19 Nov 19 Nov

8:39 a.m.

New subject: [Bug 106634] Failed to find memory space for buffer [...] eviction

https://bugs.freedesktop.org/show_bug.cgi?id=106634

Martin Peres martin.peres@free.fr changed:

--- Comment #8 from Martin Peres martin.peres@free.fr --- -- 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.

-- You are receiving this mail because: You are the assignee for the bug.

1979

Age (days ago)

2524

Last active (days ago)

dri-devel@lists.freedesktop.org

10 comments

1 participants

tags (0)

participants (1)

bugzilla-daemon＠freedesktop.org