From: Huang Rui <ray.huang@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Koenig, Christian" <Christian.Koenig@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 5.11-rc1 TTM list corruption
Date: Tue, 5 Jan 2021 20:20:26 +0800 [thread overview]
Message-ID: <20210105122026.GA227519@hr-amd> (raw)
In-Reply-To: <20210105114351.GD28649@zn.tnic>
On Tue, Jan 05, 2021 at 07:43:51PM +0800, Borislav Petkov wrote:
> On Tue, Jan 05, 2021 at 07:08:52PM +0800, Huang Rui wrote:
> > Ah, this asic is a bit old and still use radeon driver. So we didn't
> > reproduce it on amdgpu driver. I don't have such the old asic in my hand.
> > May we know whether this issue can be duplicated after SI which is used
> > amdgpu module (not sure whether you have recent APU or GPU)?
>
> The latest I have (I think it is the latest) is:
>
> [ 1.826102] [drm] initializing kernel modesetting (RENOIR 0x1002:0x1636 0x17AA:0x5099 0xD1).
>
> and so far that hasn't triggered it. Which makes sense because that
> thing uses amdgpu:
>
> [ 1.810260] [drm] amdgpu kernel modesetting enabled.
Yes! Renoir is late enough for amdgpu kernel module. :-)
Please let us know if you still encounter the issue.
Thanks,
Ray
next prev parent reply other threads:[~2021-01-05 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 10:40 5.11-rc1 TTM list corruption Borislav Petkov
2021-01-01 14:34 ` Christian König
2021-01-04 10:58 ` Borislav Petkov
2021-01-04 14:48 ` Christian König
2021-01-05 4:12 ` Huang Rui
2021-01-05 10:31 ` Borislav Petkov
2021-01-05 11:08 ` Huang Rui
2021-01-05 11:34 ` Christian König
2021-01-05 11:43 ` Borislav Petkov
2021-01-05 12:20 ` Huang Rui [this message]
2021-01-05 15:40 ` Christian König
2021-01-06 16:54 ` David Woodhouse
2021-01-06 17:10 ` Alex Deucher
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=20210105122026.GA227519@hr-amd \
--to=ray.huang@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=bp@alien8.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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