public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.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: Thu, 20 Apr 2023 11:59:17 +0200	[thread overview]
Message-ID: <b6ab0086-7d52-2a41-2f76-44694faed317@amd.com> (raw)
In-Reply-To: <CABXGCsP2JQMtNjBROSLs2y612iLZuCyoe-uD6OScAWbKHBWsCA@mail.gmail.com>

Am 19.04.23 um 21:17 schrieb Mikhail Gavrilov:
> On Wed, Apr 19, 2023 at 6:15 PM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> Well exactly that's the problem, I can't reproduce it.
>>
>> Have you applied any local change or config which could explain that?
>>
> I did not apply any local changes.
> I just pulled all changes from drm-fixes and used the attached config.
> After that I am lucky to reproduce the issue after 3 minutes.
> I recorded this on video with first take: https://youtu.be/wqD_t8AFU3s
> I able to reproduce it on various hardware:
> Ryzen 3950X + 7900XTX
> Ryzen 7950X + 6900XT
> Ryzen 5900HX + 6800M

Could you try drm-misc-next as well?

Going to give drm-fixes another round of testing.

Thanks,
Christian.

  reply	other threads:[~2023-04-20  9:59 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
2023-04-19 19:17           ` Mikhail Gavrilov
2023-04-20  9:59             ` Christian König [this message]
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=b6ab0086-7d52-2a41-2f76-44694faed317@amd.com \
    --to=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