From: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
chris@chris-wilson.co.uk,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Subject: Re: Lockdep spalt on killing a processes
Date: Mon, 1 Nov 2021 11:24:14 -0400 [thread overview]
Message-ID: <3b7db8b1-a6a0-5eb4-e674-9b33f37b1812@amd.com> (raw)
In-Reply-To: <6aa79474-e998-368b-bb53-b43f135f5a0c@amd.com>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
Pushed to drm-misc-next
Andrey
On 2021-10-29 3:07 a.m., Christian König wrote:
>>
>> Attached a patch. Give it a try please, I tested it on my side and
>> tried to generate the right conditions to trigger this code path by
>> repeatedly submitting commands while issuing GPU reset to stop the
>> scheduler and then killing command submissions process in the middle.
>> But for some reason looks like the job_queue was always empty already
>> at the time of entity kill.
>
> It was trivial to trigger with the stress utility I've hacked together:
>
> amdgpu_stress -b v 1g -b g 1g -c 1 2 1g 1k
>
> Then while it is copying just cntrl+c to kill it.
>
> The patch itself is:
>
> Tested-by: Christian König <christian.koenig@amd.com>
> Reviewed-by: Christian König <christian.koenig@amd.com>
>
> Thanks,
> Christian.
[-- Attachment #2: Type: text/html, Size: 1620 bytes --]
prev parent reply other threads:[~2021-11-01 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 10:50 Lockdep spalt on killing a processes Christian König
2021-10-01 14:52 ` Daniel Vetter
2021-10-01 15:10 ` Andrey Grodzovsky
2021-10-04 8:14 ` Christian König
2021-10-04 15:27 ` Andrey Grodzovsky
2021-10-20 19:32 ` Andrey Grodzovsky
2021-10-21 6:34 ` Christian König
2021-10-25 19:10 ` Andrey Grodzovsky
2021-10-25 19:56 ` Christian König
2021-10-26 2:33 ` Andrey Grodzovsky
2021-10-26 10:54 ` Christian König
2021-10-27 14:27 ` Andrey Grodzovsky
2021-10-27 14:34 ` Christian König
2021-10-27 14:47 ` Andrey Grodzovsky
2021-10-27 14:50 ` Christian König
2021-10-27 19:58 ` Andrey Grodzovsky
2021-10-28 17:26 ` Andrey Grodzovsky
2021-10-29 7:07 ` Christian König
2021-11-01 15:24 ` Andrey Grodzovsky [this message]
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=3b7db8b1-a6a0-5eb4-e674-9b33f37b1812@amd.com \
--to=andrey.grodzovsky@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--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.