From: bugzilla-daemon--- via dri-devel <dri-devel@lists.freedesktop.org>
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202537] amdgpu/DC failed to reserve new abo buffer before flip
Date: Fri, 15 Feb 2019 22:37:09 +0000 [thread overview]
Message-ID: <bug-202537-2300-UCZ9burZTN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202537-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202537
--- Comment #11 from Bernd Steinhauser (linux@bernd-steinhauser.de) ---
Ok, so finally I think I've been able to track this down.
Not 100% sure, because for the final test versions I had to apply a few patches
to fix bugs that otherwise would've prevented tests.
In any case, this was the first version that showed this massive amount of
memleaks, before there were only 6 (of which 4 were related to HID and ACPI).
5d35ed4832dab334e076a24c18a52776c2f24911 is the first bad commit
commit 5d35ed4832dab334e076a24c18a52776c2f24911
Author: Christian König <christian.koenig@amd.com>
Date: Fri Aug 31 11:08:06 2018 +0200
drm/amdgpu: fix idle state and bulk_moveable flag
····
Add BOs to the idle state again and correctly clear the flag when
new BOs are added.
····
Signed-off-by: Christian König <christian.koenig@amd.com>
Tested-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
:040000 040000 28e778e55b368e605e6f2df4efea4be5f324d4ae
371220da179e31b7d2c97741dd984cb896fcb4c4 M drivers
--
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 prev parent reply other threads:[~2019-02-15 22:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 14:17 [Bug 202537] New: amdgpu/DC failed to reserve new abo buffer before flip bugzilla-daemon
2019-02-09 14:27 ` [Bug 202537] " 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 [this message]
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-UCZ9burZTN@https.bugzilla.kernel.org/ \
--to=dri-devel@lists.freedesktop.org \
--cc=bugzilla-daemon@bugzilla.kernel.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.