From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "amd-gfx list" <amd-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"Christian König" <Christian.Koenig@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>
Subject: Re: BUG: KASAN: null-ptr-deref in drm_sched_job_cleanup+0x96/0x290 [gpu_sched]
Date: Wed, 19 Apr 2023 15:15:13 +0200 [thread overview]
Message-ID: <d96519fb-9e12-5a81-a60b-384dcb286f28@gmail.com> (raw)
In-Reply-To: <CABXGCsPcPY8dqZm0aF4c1p0ZvMYHy+NksMrZi9xK0=WdE5_osA@mail.gmail.com>
Am 19.04.23 um 15:13 schrieb Mikhail Gavrilov:
> On Wed, Apr 19, 2023 at 1:12 PM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> I'm already looking into this, but can't figure out why we run into
>> problems here.
>>
>> What happens is that a CS is aborted without sending the job to the
>> scheduler and in this case the cleanup function doesn't seem to work.
>>
>> Christian.
> I can easily reproduce it on any AMD GPU hardware.
Well exactly that's the problem, I can't reproduce it.
Have you applied any local change or config which could explain that?
Christian.
> You can add more logs to debug and I return with new logs which explains this.
> Thanks.
>
next prev parent reply other threads:[~2023-04-19 13:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 17:40 BUG: KASAN: null-ptr-deref in drm_sched_job_cleanup+0x96/0x290 [gpu_sched] Mikhail Gavrilov
2023-04-14 15:08 ` Mikhail Gavrilov
2023-04-19 7:00 ` Mikhail Gavrilov
2023-04-19 8:12 ` Christian König
2023-04-19 13:13 ` Mikhail Gavrilov
2023-04-19 13:15 ` Christian König [this message]
2023-04-19 19:17 ` Mikhail Gavrilov
2023-04-20 9:59 ` Christian König
2023-04-20 10:32 ` Mikhail Gavrilov
2023-04-25 13:19 ` Mikhail Gavrilov
2023-04-26 2:00 ` Chen, Guchun
2023-04-26 11:48 ` Keyword Review - " Christian König
2023-04-26 11:50 ` Christian König
2023-05-02 19:28 ` Mikhail Gavrilov
2023-04-20 21:24 ` 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=d96519fb-9e12-5a81-a60b-384dcb286f28@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Christian.Koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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