From: Steven Rostedt <rostedt@goodmis.org>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Matthew Auld" <matthew.william.auld@gmail.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Arunpravin Paneer Selvam" <Arunpravin.PaneerSelvam@amd.com>,
intel-gfx@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Felix Kuehling" <Felix.Kuehling@amd.com>,
linux-media@vger.kernel.org
Subject: Re: [Intel-gfx] [BUG 6.3-rc1] Bad lock in ttm_bo_delayed_delete()
Date: Wed, 15 Mar 2023 16:20:11 -0400 [thread overview]
Message-ID: <20230315162011.351d0f71@gandalf.local.home> (raw)
In-Reply-To: <2b7fe203-82f5-2726-cd64-01c7421560d3@amd.com>
On Wed, 15 Mar 2023 20:51:49 +0100
Christian König <christian.koenig@amd.com> wrote:
> Steven please try the attached patch.
I applied it, but as it's not always reproducible, I'll have to give it
several runs before I give you my "tested-by" tag.
-- Steve
next prev parent reply other threads:[~2023-03-15 20:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 2:22 [BUG 6.3-rc1] Bad lock in ttm_bo_delayed_delete() Steven Rostedt
2023-03-08 2:26 ` Steven Rostedt
2023-03-08 6:17 ` Christian König
2023-03-08 12:43 ` Steven Rostedt
2023-03-15 18:41 ` Christian König
2023-03-15 19:15 ` [Intel-gfx] " Matthew Auld
2023-03-15 19:51 ` Christian König
2023-03-15 20:20 ` Steven Rostedt [this message]
2023-03-16 0:21 ` Steven Rostedt
2023-03-16 0:22 ` Steven Rostedt
2023-03-17 17:42 ` Linus Torvalds
2023-03-15 15:09 ` Steven Rostedt
2023-03-15 15:25 ` Christian König
2023-03-15 15:57 ` Steven Rostedt
2023-03-15 17:31 ` Steven Rostedt
2023-03-15 18:34 ` Christian König
2023-03-15 17:54 ` Steven Rostedt
2023-03-15 18:25 ` Christian König
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=20230315162011.351d0f71@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.william.auld@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox