From: "Christian König" <christian.koenig@amd.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Robin McCorkell <robin@mccorkell.me.uk>
Cc: linux-pci@vger.kernel.org, stable@vger.kernel.org,
Nirmoy Das <nirmoy.das@amd.com>
Subject: Re: [PATCH v2] PCI: Limit REBAR quirk to just Sapphire RX 5600 XT Pulse
Date: Tue, 2 Nov 2021 13:27:02 +0100 [thread overview]
Message-ID: <c87ab346-ab44-1bc7-767a-e40a9c9f5cef@amd.com> (raw)
In-Reply-To: <20211101215516.GA554197@bhelgaas>
Am 01.11.21 um 22:55 schrieb Bjorn Helgaas:
> [+cc Christian, Nirmoy]
>
> On Tue, Oct 26, 2021 at 10:44:59PM +0100, Robin McCorkell wrote:
>> A particular RX 5600 device requires a hack in the rebar logic, but the
>> current branch is too general and catches other devices too, breaking
>> them. This patch changes the branch to be more selective on the
>> particular revision.
>>
>> This patch fixes intermittent freezes on other RX 5600 devices where the
>> hack is unnecessary. Credit to all contributors in the linked issue on
>> the AMD bug tracker.
>>
>> See also: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues%2F1707&data=04%7C01%7Cchristian.koenig%40amd.com%7Cfa71c149d6084ca3254508d99d824b9b%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637714005225516666%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Vu%2FVbyBEGrnTjqcmAkJDJHa1BbUICRkSB1Jfre%2BhDhM%3D&reserved=0
>>
>> Fixes: 907830b0fc9e ("PCI: Add a REBAR size quirk for Sapphire RX 5600 XT Pulse")
>> Cc: stable@vger.kernel.org # v5.12+
>> Signed-off-by: Robin McCorkell <robin@mccorkell.me.uk>
>> Reported-by: Simon May <@Socob on gitlab.freedesktop.com>
>> Tested-by: Kain Centeno <@kaincenteno on gitlab.freedesktop.com>
>> Tested-by: Tobias Jakobi <@tobiasjakobi on gitlab.freedesktop.com>
>> Suggested-by: lijo lazar <@lijo on gitlab.freedesktop.com>
> I'll wait for an ack from Christian on this one, since it doesn't seem
> to make sense to him.
Please just completely drop the patch for now.
It's really interesting that resizing the BAR makes the problem on that
hardware more likely to appear, but we have already found people
reporting issues even with the patch in question completely reverted.
So that is most likely not the root cause and we need to dig deeper.
Thanks,
Christian.
>
>> ---
>> drivers/pci/pci.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
>> index ce2ab62b64cf..1fe75243019e 100644
>> --- a/drivers/pci/pci.c
>> +++ b/drivers/pci/pci.c
>> @@ -3647,7 +3647,7 @@ u32 pci_rebar_get_possible_sizes(struct pci_dev *pdev, int bar)
>>
>> /* Sapphire RX 5600 XT Pulse has an invalid cap dword for BAR 0 */
>> if (pdev->vendor == PCI_VENDOR_ID_ATI && pdev->device == 0x731f &&
>> - bar == 0 && cap == 0x7000)
>> + pdev->revision == 0xC1 && bar == 0 && cap == 0x7000)
>> cap = 0x3f000;
>>
>> return cap >> 4;
>> --
>> 2.31.1
>>
next prev parent reply other threads:[~2021-11-02 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 20:46 [PATCH] Limit AMD Radeon rebar hack to a single revision Robin McCorkell
2021-10-26 21:28 ` Bjorn Helgaas
2021-10-26 21:44 ` [PATCH v2] PCI: Limit REBAR quirk to just Sapphire RX 5600 XT Pulse Robin McCorkell
2021-10-27 9:47 ` Krzysztof Wilczyński
2021-11-01 21:55 ` Bjorn Helgaas
2021-11-02 12:27 ` Christian König [this message]
2021-10-26 21:49 ` [PATCH] Limit AMD Radeon rebar hack to a single revision Robin McCorkell
2021-10-27 6:38 ` 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=c87ab346-ab44-1bc7-767a-e40a9c9f5cef@amd.com \
--to=christian.koenig@amd.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nirmoy.das@amd.com \
--cc=robin@mccorkell.me.uk \
--cc=stable@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).