From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202537] New: amdgpu/DC failed to reserve new abo buffer before flip
Date: Sat, 09 Feb 2019 14:17:05 +0000 [thread overview]
Message-ID: <bug-202537-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=202537
Bug ID: 202537
Summary: amdgpu/DC failed to reserve new abo buffer before flip
Product: Drivers
Version: 2.5
Kernel Version: 4.20
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: linux@bernd-steinhauser.de
Regression: No
I've been using amdgpu for a long time on my Kaveri (A7800) now and it works
fine.
In the recent kernel versions (I think since 4.15), I've been trying it with
the DC activated and apart from some initial issue with the HDMI connection it
works fine and on 4.19 it's rock-stable.
However, when I tried 4.20 (all versions from 4.20.1 to 4.20.6), I'm
experiencing a regression.
Initially, everything works fine, but at some point especially video-related
things stop working properly.
vaapi seems more affected than vdpau, but at some point they both fail to setup
the hw decoding.
(btw, vdpau for some reason can only run for one video at the time, while vaapi
can do multiple ones, but that's an unrelated issue. It used to be different a
year ago or even earlier on)
I think the problems start when I see a lot of messages like this:
[drm:amdgpu_display_crtc_page_flip_target] *ERROR* failed to reserve new abo
buffer before flip
However, after that I can continue for a bit, possibly with the restriction of
not being able to use vaapi but vdpau.
At some point, the system will fail due to a memory leak, at least the OOM is
starting to kill stuff until it ends up killing the window manager and X11.
Before that I get these messages:
[drm:amdgpu_cs_ioctl] *ERROR* amdgpu_vm_validate_pt_bos() failed.
[drm:amdgpu_cs_ioctl] *ERROR* Not enough memory for command submission!
[drm:amdgpu_cs_ioctl] *ERROR* amdgpu_cs_list_validate(validated) failed.
[drm:amdgpu_cs_ioctl] *ERROR* Not enough memory for command submission!
[drm:amdgpu_cs_ioctl] *ERROR* amdgpu_vm_validate_pt_bos() failed.
[drm:amdgpu_cs_ioctl] *ERROR* Not enough memory for command submission!
--- snip --- (lots of oom activity)
and finally:
[TTM] Out of kernel memory
[TTM] Out of kernel memory
[TTM] Out of kernel memory
[TTM] Out of kernel memory
[TTM] Out of kernel memory
[TTM] Out of kernel memory
[TTM] Out of kernel memory
amdgpu 0000:00:01.0: (-12) failed to allocate kernel bo
[drm:amdgpu_uvd_free_handles] *ERROR* Error destroying UVD -12!
The latter one – I think – actually being the solution to the OOM problem, but
I'm certainly not an expert.
CPU/GPU is:
vendor_id : AuthenticAMD
cpu family : 21
model : 48
model name : AMD A10-7800 Radeon R7, 12 Compute Cores 4C+8G
stepping : 1
microcode : 0x6003106
cpu MHz : 1592.730
cache size : 2048 KB
Back to 4.19 for now since that runs beautifully.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-02-09 14:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 14:17 bugzilla-daemon [this message]
2019-02-09 14:27 ` [Bug 202537] amdgpu/DC failed to reserve new abo buffer before flip bugzilla-daemon
2019-02-11 10:47 ` bugzilla-daemon
2019-02-11 17:09 ` bugzilla-daemon
2019-02-11 17:20 ` bugzilla-daemon
2019-02-11 17:50 ` bugzilla-daemon
2019-02-11 18:59 ` bugzilla-daemon
2019-02-12 9:07 ` bugzilla-daemon--- via dri-devel
2019-02-12 15:15 ` bugzilla-daemon--- via dri-devel
2019-02-12 17:09 ` bugzilla-daemon--- via dri-devel
2019-02-14 7:34 ` bugzilla-daemon--- via dri-devel
2019-02-15 22:37 ` bugzilla-daemon--- via dri-devel
2019-02-16 19:17 ` bugzilla-daemon--- via dri-devel
2019-02-17 8:07 ` bugzilla-daemon--- via dri-devel
2019-02-17 8:36 ` bugzilla-daemon--- via dri-devel
2019-02-17 8:57 ` bugzilla-daemon--- via dri-devel
2019-02-17 10:00 ` bugzilla-daemon--- via dri-devel
2019-02-18 7:45 ` bugzilla-daemon
2019-02-18 8:08 ` bugzilla-daemon
2019-02-18 9:02 ` bugzilla-daemon
2019-02-18 22:26 ` bugzilla-daemon
2019-02-18 22:28 ` bugzilla-daemon
2019-02-19 19:27 ` bugzilla-daemon
2019-02-19 21:00 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-202537-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.