From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: "Huang, Ray" <Ray.Huang@amd.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Anthony Wong <anthony.wong@canonical.com>
Subject: Re: [Regression] "drm/amdgpu: enable gfxoff again on raven series (v2)"
Date: Thu, 8 Aug 2019 14:40:35 +0800 [thread overview]
Message-ID: <94CAE10C-1C2D-4A62-A26B-971A8EEE277A@canonical.com> (raw)
In-Reply-To: <MN2PR12MB3309680845257BC66644133CECD70@MN2PR12MB3309.namprd12.prod.outlook.com>
at 14:29, Huang, Ray <Ray.Huang@amd.com> wrote:
>> -----Original Message-----
>> From: Kai-Heng Feng <kai.heng.feng@canonical.com>
>> Sent: Thursday, August 08, 2019 1:45 AM
>> To: Huang, Ray <Ray.Huang@amd.com>
>> Cc: Deucher, Alexander <Alexander.Deucher@amd.com>; Koenig, Christian
>> <Christian.Koenig@amd.com>; Zhou, David(ChunMing)
>> <David1.Zhou@amd.com>; amd-gfx list <amd-gfx@lists.freedesktop.org>;
>> dri-devel@lists.freedesktop.org; LKML <linux-kernel@vger.kernel.org>;
>> Anthony Wong <anthony.wong@canonical.com>
>> Subject: Re: [Regression] "drm/amdgpu: enable gfxoff again on raven series
>> (v2)"
>>
>> Hi Ray,
>>
>> at 00:03, Huang, Ray <Ray.Huang@amd.com> wrote:
>>
>>> May I know the all firmware version in your system?
>
> Seems to the issue we encountered with IOMMU enabled. Could you please
> disable iommu in SBIOS or GRUB?
Yes, "amd_iommu=off" can workaround the issue.
Kai-Heng
>
> Thanks,
> Ray
>
>> # cat amdgpu_firmware_info
>> VCE feature version: 0, firmware version: 0x00000000
>> UVD feature version: 0, firmware version: 0x00000000
>> MC feature version: 0, firmware version: 0x00000000
>> ME feature version: 40, firmware version: 0x00000099
>> PFP feature version: 40, firmware version: 0x000000ae
>> CE feature version: 40, firmware version: 0x0000004d
>> RLC feature version: 1, firmware version: 0x00000213
>> RLC SRLC feature version: 1, firmware version: 0x00000001
>> RLC SRLG feature version: 1, firmware version: 0x00000001
>> RLC SRLS feature version: 1, firmware version: 0x00000001
>> MEC feature version: 40, firmware version: 0x0000018b
>> MEC2 feature version: 40, firmware version: 0x0000018b
>> SOS feature version: 0, firmware version: 0x00000000
>> ASD feature version: 0, firmware version: 0x001ad4d4
>> TA XGMI feature version: 0, firmware version: 0x00000000
>> TA RAS feature version: 0, firmware version: 0x00000000
>> SMC feature version: 0, firmware version: 0x00001e44
>> SDMA0 feature version: 41, firmware version: 0x000000a9
>> VCN feature version: 0, firmware version: 0x0110901c
>> DMCU feature version: 0, firmware version: 0x00000000
>> VBIOS version: 113-RAVEN-103
>>
>> Kai-Heng
>>
>>> Thanks,
>>> Ray
>>>
>>> From: Kai-Heng Feng <kai.heng.feng@canonical.com>
>>> Sent: Wednesday, August 7, 2019 8:50 PM
>>> To: Huang, Ray
>>> Cc: Deucher, Alexander; Koenig, Christian; Zhou, David(ChunMing); amd-
>> gfx
>>> list; dri-devel@lists.freedesktop.org; LKML; Anthony Wong
>>> Subject: [Regression] "drm/amdgpu: enable gfxoff again on raven series
>>> (v2)"
>>>
>>> Hi,
>>>
>>> After commit 005440066f92 ("drm/amdgpu: enable gfxoff again on raven
>> series
>>> (v2)”), browsers on Raven Ridge systems cause serious corruption like
>>> this:
>>> https://launchpadlibrarian.net/436319772/Screenshot%20from%202019-
>> 08-07%2004-20-34.png
>>> Firmwares for Raven Ridge is up-to-date.
>>>
>>> Kai-Heng
next prev parent reply other threads:[~2019-08-08 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 12:50 [Regression] "drm/amdgpu: enable gfxoff again on raven series (v2)" Kai-Heng Feng
[not found] ` <MN2PR12MB330979BAFF5BCC758258D54CECD40@MN2PR12MB3309.namprd12.prod.outlook.com>
2019-08-07 17:44 ` Kai-Heng Feng
2019-08-08 6:29 ` Huang, Ray
2019-08-08 6:40 ` Kai-Heng Feng [this message]
2019-08-08 8:10 ` Michel Dänzer
2019-08-08 8:14 ` Huang, Ray
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=94CAE10C-1C2D-4A62-A26B-971A8EEE277A@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=David1.Zhou@amd.com \
--cc=Ray.Huang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=anthony.wong@canonical.com \
--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;
as well as URLs for NNTP newsgroup(s).