public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Mario Limonciello <superm1@kernel.org>,
	Bert Karwatzki <spasswolf@web.de>,
	linux-kernel@vger.kernel.org
Cc: linux-next@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem"
Date: Mon, 2 Feb 2026 15:35:31 +0100	[thread overview]
Message-ID: <b978d83d-3bd2-4ef0-8a2c-eb756a880fa4@amd.com> (raw)
In-Reply-To: <02fe7f9e-f25b-4b6b-8420-57de982147bd@kernel.org>

On 2/2/26 15:25, Mario Limonciello wrote:
> On 1/31/26 6:24 PM, Bert Karwatzki wrote:
>> This reverts commit 7294863a6f01248d72b61d38478978d638641bee.
>>
>> This commit was erroneously applied again after commit 0ab5d711ec74
>> ("drm/amd: Refactor `amdgpu_aspm` to be evaluated per device")
>> removed it, leading to very hard to debug crashes, when used with a system with two
>> AMD GPUs of which only one supports ASPM.
>>
>> Link: https://lore.kernel.org/linux-acpi/20251006120944.7880-1-spasswolf@web.de/
>> Link: https://github.com/acpica/acpica/issues/1060
>> Fixes: 0ab5d711ec74 ("drm/amd: Refactor `amdgpu_aspm` to be evaluated per device")
>>
>> Signed-off-by: Bert Karwatzki <spasswolf@web.de>
>> ---
> 
> Amazing detective work, thanks so much.
> 
> This added the code initially:
> cba07cce39ace drm/amd: Check if ASPM is enabled from PCIe subsystem
> 
> This effectively removed it:
> 0ab5d711ec74d drm/amd: Refactor `amdgpu_aspm` to be evaluated per device
> 
> This was the accidental re-apply:
> 7294863a6f012 drm/amd: Check if ASPM is enabled from PCIe subsystem
> 
> It looks like this as right on the edge of the 5.17-rc6 and 5.18-rc1.
> I think drm-fixes-2022-02-25 and amd-drm-next-5.18-2022-02-25 ended up with different content.
> 
> Nonethless this is the correct change and I've applied it to amd-staging-drm-next.
> 
> Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>

Reviewed-by: Christian König <christian.koenig@amd.com>

There is just one major question left: Why is disabling ASPM causing problems?

I mean we had tons of problems with ASPM before, but only by accidentally enabling it and never accidentally disabling it.

IIRC we even suggested to disable ASPM as possible workaround.

Thanks,
Christian.

> 
>>   drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 ---
>>   1 file changed, 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
>> index d6d0a6e34c6b..95d26f086d54 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
>> @@ -2405,9 +2405,6 @@ static int amdgpu_pci_probe(struct pci_dev *pdev,
>>               return -ENODEV;
>>       }
>>   -    if (amdgpu_aspm == -1 && !pcie_aspm_enabled(pdev))
>> -        amdgpu_aspm = 0;
>> -
>>       if (amdgpu_virtual_display ||
>>           amdgpu_device_asic_has_dc_support(pdev, flags & AMD_ASIC_MASK))
>>           supports_atomic = true;
> 


  reply	other threads:[~2026-02-02 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01  0:24 [PATCH] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" Bert Karwatzki
2026-02-02 14:25 ` Mario Limonciello
2026-02-02 14:35   ` Christian König [this message]
2026-02-02 16:11     ` Mario Limonciello
2026-02-02 16:43       ` Bert Karwatzki

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=b978d83d-3bd2-4ef0-8a2c-eb756a880fa4@amd.com \
    --to=christian.koenig@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=spasswolf@web.de \
    --cc=superm1@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