From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
michel@daenzer.net, Borislav Petkov <bp@alien8.de>,
amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: grab extra fence reference for drm_sched_job_add_dependency
Date: Thu, 12 Jan 2023 13:05:43 +0100 [thread overview]
Message-ID: <b2608d35-00e6-3935-3f87-297270be7073@gmail.com> (raw)
In-Reply-To: <CABXGCsPpTTVXMTtZi_Yw_27VHHnPL_XSidMENzRniWZgZXd_NA@mail.gmail.com>
Am 10.01.23 um 19:21 schrieb Mikhail Gavrilov:
> On Mon, Jan 9, 2023 at 6:40 PM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> That looks like an out of memory situation is not gracefully handled.
>>
>> In other words we have a missing NULL check in drm_sched_job_cleanup().
>>
>> Going to take a look.
> Very strange because it just reproduced again. Almost no memory leaked.
>
> ❯ free
> total used free shared buff/cache available
> Mem: 65589600 34060388 1520668 3033284 30008544 27767260
> Swap: 75497464 994560 74502904
Mhm, our UVD guys reported similar problems when they open up to many
concurrent streams.
Most likely some random issue cause by one of the gang submit patches.
Could you try to better reproduce this? If we can reproduce this
reliable compiling the kernel with KASAN might help figuring out where
exactly something goes wrong.
Christian.
>
>
>
>
>
> --
> Best Regards,
> Mike Gavrilov.
next prev parent reply other threads:[~2023-01-12 12:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 10:47 [PATCH] drm/amdgpu: grab extra fence reference for drm_sched_job_add_dependency Christian König
2022-12-19 14:00 ` Borislav Petkov
2022-12-21 21:10 ` Alex Deucher
2023-01-03 8:34 ` Christian König
2023-01-03 14:26 ` Alex Deucher
2023-01-03 14:28 ` Michel Dänzer
2023-01-05 1:44 ` Mikhail Gavrilov
2023-01-05 10:03 ` Christian König
2023-01-06 12:59 ` Mikhail Gavrilov
2023-01-06 14:24 ` Alex Deucher
2023-01-06 15:27 ` Christian König
2023-01-09 13:13 ` Mikhail Gavrilov
2023-01-09 13:40 ` Christian König
2023-01-10 18:21 ` Mikhail Gavrilov
2023-01-12 12:05 ` Christian König [this message]
2022-12-19 15:08 ` Luben Tuikov
2022-12-23 10:00 ` Michal Kubecek
2022-12-23 22:55 ` Mikhail Gavrilov
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=b2608d35-00e6-3935-3f87-297270be7073@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bp@alien8.de \
--cc=michel@daenzer.net \
--cc=mikhail.v.gavrilov@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox