All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Bert Karwatzki" <spasswolf@web.de>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	stable@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 6.18.8] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem"
Date: Tue, 3 Feb 2026 15:52:17 +0100	[thread overview]
Message-ID: <2026020308-darling-corroding-d951@gregkh> (raw)
In-Reply-To: <2fcded69-e458-431d-886b-b76c7e3fd9d0@amd.com>

On Tue, Feb 03, 2026 at 08:42:15AM -0600, Mario Limonciello wrote:
> On 2/3/26 8:39 AM, Greg KH wrote:
> > On Sun, Feb 01, 2026 at 01:25:06AM +0100, 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>
> > > ---
> > >   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 7333e19291cf..ec9516d6ae97 100644
> > > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > > @@ -2334,9 +2334,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;
> > > -- 
> > > 2.47.3
> > > 
> > > 
> > 
> > 
> > <formletter>
> > 
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree.  Please read:
> >      https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> > 
> > </formletter>
> 
> FWIW I added a stable tag to the patch when applied to amd-staging-drm-next
> for this.  So it should come back to stable once it merges in Linus' tree.

Great, thanks!

greg k-h

      reply	other threads:[~2026-02-04  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-01  0:25 [PATCH 6.18.8] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" Bert Karwatzki
2026-02-03 14:39 ` Greg KH
2026-02-03 14:42   ` Mario Limonciello
2026-02-03 14:52     ` Greg KH [this message]

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=2026020308-darling-corroding-d951@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=spasswolf@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.